The flow definitions have been modified outside of Automagic

[Viking84]

Hi all,

Since about 2 weeks I'm receiving the error message "The flow definitions have been modified outside of Automagic", see screenshot attached.

I think this happened after upgrading Automagic, but I'm not 100% sure of that; however I did not modify any file outside of the app, nor did any other app modify them. When I acknowledge the message and reactivate all flows, they work until the moment the phone reboots, then everything stops again. And the worst thing is that I'm not even receiving a popup notification, but only get to see the error when I open Automagic, wondering why certain variables have not been set.

Given that I use my flows for some tasks that need to be executed every morning by 5am, I need a way to restore the functionality ASAP.

I'm on a OnePlus One with CyanogenMod 11.0-XNPH44S in case that matters.

Thanks a lot in advance!

[Martin]

Hi,

Are you using some kind of privacy app/tool that modifies the device ID on each boot?

If not, then please follow this procedure to create a debug log:
-enable Debug Log and Log to SD card in the preferences of Automagic
-modify one flow in some way so that Automagic saves the flows
-reboot the device
-start Automagic so that the error is displayed
-send the log to me with menu->Manage->Log, menu->Send Log (send to info@automagic4android.com)

Regards,
Martin

[Viking84]

Ah, yes I do indeed use Xprivacy to generate a new ID upon booting, wasn't aware that this has an impact on automagic... I will try assigning a fixed ID and see if that resolves the problem, thanks!

Best,
Chris

[uveequis]

I am having the same problem. It happened after flashing a new ROM (the same ROM, new version actually) and trying to restore app+data using Titanium Backup. I tried extracting app data from a naandroid backup too, with the same result. I never had problems restoring the flows this way so I didn't export them using the Automagic option. I hope there is some way to restore them because it would be really hard to remember and rewrite all of them again.

[Martin]

Hi,

Maybe the device ID changed. Newer versions of Automagic should not show this error anymore in such cases. Are you using the latest version of Automagic?
Are the flows not loaded when clicking 'yes' in the verify dialog?

Regards,
Martin

[uveequis]

I recall some other app telling me the ID had indeed changed. I just tried installing first the latest version of Automagic (1.29.0) from the Play Store before restoring the app data (I had tried before restoring all app+data) but said Verify Error message pops up. When I click 'yes' it shows a similar message about the custom widgets and if I click 'yes' again it just loads the default example flows.

EDIT: I found this app, Naandroid Manager, which allowed me to restore the previous ID. This ID comes from the same backup where the Automagic app data is extracted from but I still get the same error!

[Martin]

Can you please send the flows.xml and widgets.xml from the backup to me (info@automagic4android.com) maybe the data got corrupted somehow.

Following procedure should also wok when the files are not corrupted:
1) Uninstall Automagic
2) Copy flows.xml and widgets.xml from your backup to /storage/emulated/0/Automagic/
3) Install Automagic from Google Play and start Automagic

[uveequis]

I'm afraid I can't extract those files from the naandroid backup. So I'm just giving up and will slowly re-write them. Thank you anyway!

[kintrupf]

Why is there no third option in the warning dialog to load the flows AND keep those enabled that were enabled before?
Lately I updated the ROM of my phone, restored Automagic with Titanium Backup and was presented with this "Flows changed outside" message.
Naturally I choose to load the flows, but then I had to painstakingly walk through all my flows (100+) to re-enabled them

I would really like to have either that third option in the load dialog or an (advanced) preference to disable this check altogether.
Thanks!

[Martin]

I'll probably add such a third option. It seems that the check causes more problems than it helps. When the flows are available on /storage/emulated/0/Automagic, you could force-stop Automagic, clear the data of Automagic and the flows should be loaded without warning.