StateSaver doesn't work anymore on mobile when app is installed from QtCreator

Grml, grml, it does work when I run the app *on the device* from QtCreator, but it does not with the app I've installed on the device (still from QtCreator).

Yep, maybe it doesn't work when run under confinement? Looks like an SDK bug to me.

The (weird) fact is that it does work with 0.1.1 version, which had same apparmor policy afaik.

I've tried to add "template=unconfined" in the AppArmor settings file, but the behaviour is the same. :/

Reverted to rev 48 (last rev before releasing 0.1.1), reinstalled app from QtCreator, and the behaviour is still the same.
So there is a great chance that the problem is linked to the way the app is installed, or something else on my local configuration, so I'm closing for now, and will release a 0.1.2 and we will see.

Or a regression in the sdk...

Is it working for you, with new version, btw?

Nope, still broken.

Here's an idea. Add a quit button, and see if it works after quitting the app cleanly.

If it saves the data on exit, then this should work.

The application lifecycle stuff is still not completed as far as I am aware. This means that when you close an app, you are literally just killing it, and anything that should run on exit will never be run.

If that turns out to be the case, then just don't worry about it, it should be fixed when the lifecycle stuff is fully functioning.

Same when using "Qt.quit()" for quitting.
Other fact: I've asked for people to test on IRC, and the StateSaver was working for the one who answered (using a Nexus5, but not sure it's important).

StateSaver is a feature implemented by the SDK devs and is designed to save states in case of application suspend or crash or other emergency situations. On a clean exit, it *discards* the state. Unfortunately this was made clear in their documentation. However the good news is that there is a bug report tracking the "permanent state saving feature" at https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1296669.

I meant that this was unfortunately *not* made clear in the documentation ;)