Recover macros from app?

[itneveroccurred]

Since I basically can't open macrodroid without it crashing instantly, I've gone down the backup.ab rabbit hole and got stuck trying to change it to a .tar to see if all my macros are somehow in there, but it doesn't look like I'll figure that out anytime soon since I'm stuck with all this command prompt stuff. So does anyone have any methods to recover your macros without exporting them through the app? Until then I'm gonna keep going at this method and hopefully I get somewhere soon.

 

[Jacob L]

You might be able to get macros from /storage/emulated/0/MacroDroid or /storage/emulated/0/Android/ or if you're rooted /data/data. If it opens enough to hit the disable switch, then you can recover them.
You may or may not be able to export them by making the macro on another device - that exports macros or at least that disables MacroDroid to allow you into the tiles. Logcat may help identify the crash.
You could try getting MacroDroid installed in another device or another user on your device to see if you've got cloud backups from recently. If you do recover them you'll need to fix the issue before you allow them to run

 

[itneveroccurred]

You might be able to get macros from /storage/emulated/0/MacroDroid or /storage/emulated/0/Android/ or if you're rooted /data/data. If it opens enough to hit the disable switch, then you can recover them.
You may or may not be able to export them by making the macro on another device - that exports macros or at least that disables MacroDroid to allow you into the tiles. Logcat may help identify the crash.
You could try getting MacroDroid installed in another device or another user on your device to see if you've got cloud backups from recently. If you do recover them you'll need to fix the issue before you allow them to run

Ended up having to ultimately reinstall and redo the progress I made since my last save, but I'm staying away from using the write to file action from now on because the crash loop happened again, this time I luckily saved everything. Am I the only one experiencing this though?

 

[Jacob L]

Ended up having to ultimately reinstall and redo the progress I made since my last save, but I'm staying away from using the write to file action from now on because the crash loop happened again, this time I luckily saved everything. Am I the only one experiencing this though?

I suggest instead using the echo command in the shell script action. for example, echo "test" > storage/emulated/0/test.txt. There are two methods, the method with the > and the method with >>. One appends and one overwrites. If you tick the save output to string variable then if it fails then it will tell you. You may need to tick use helper, and have helper 1.7 installed

 

[itneveroccurred]

I suggest instead using the echo command in the shell script action. for example, echo "test" > storage/emulated/0/test.txt. There are two methods, the method with the > and the method with >>. One appends and one overwrites. If you tick the save output to string variable then if it fails then it will tell you. You may need to tick use helper, and have helper 1.7 installed

Oh cool ya I'll try using that method then.

 

[MacroDroidDev]

@itneveroccurred if you submit a bug report and reference this forum thread I can try and search for your exact device type in my logs to see if I can identify where the app was crashing in your case.

(You don't need to select any particular macro in this case).