Working with the app

Keep sign-in between sessions

Save the app's data when you stop a session and start the next one already signed in, past onboarding.

Why: you test the checkout every day, and every day you sign in, confirm a code and skip five onboarding screens first. Save that once and start from it.

What happens

App data is what the app keeps on the device for itself: who is signed in, settings, databases, the WebView’s cookies and local storage.

Get the app into the state you want: signed in, onboarding done, a test cart filled.
Press Save app data on the App card, or simply Stop the session: stopping saves the data too.
Next time, in the launch dialog, pick your save instead of Fresh install. Tick Also restore the cache if you want cached files back as well.
The progress list shows Restoring app data, and the app opens where you left it.

Good to know

Saves are yours only: nobody else sees them, admins included. The App data page in the header lists them; you can download or delete them there.
Only a few recent saves per app are kept, and saves nobody used for a while are deleted (by default 6 saves and 7 days).
The quick launch button (the lightning icon) can start straight from your newest save.
A save from a newer build may not work in an older one, for example when its database can’t be downgraded. The launch dialog warns you.

If it doesn’t work

There is no App data section in the launch dialog: saving is turned off on this server. Ask whoever runs Holtdroid.
The app signs you out anyway: some apps encrypt their data with keys that stay on the original device (Android Keystore). Such data can’t move to another device; this is a limit of Android, not of the save.
Stop takes long: it waits for the save to finish. A big app with a big cache saves longer.

More details: App data.