Device: Samsung Galaxy Tab Active 2
OS: Android 9
Agent Version: Android Plus ELM 14.5.0.1011 (latest)
So I have a lockdown screen with various apps (including our own). Usually, I would setup the lockdown with "launch:(...)".
This has been working just fine on our other devices for years... But for the Samsung Tab Active 2, I wasn't able to send the app in the background and restore where I left. So I added "Launchalwayswithrecents:" on the desired apps.
1) issue: We now have this warning in the Logs:
"Custom log (LaunchAlwaysWithRecents has been superseded by LaunchWithRecents and is now deprecated. It may be removed in the future.)"
No big deal. I guess Launchwithrecents will do the same...
2) I would like to be able to switch between app without restarting the app from the start all the time... especially with our app. the Regular launch is working fine on other devices...
3) fixing the issue by adding launchwithrecents causes new issues when we have crashes in our app... it restores in a mixed state all the time. the regular "launch" makes it work when we have crashes...
so... after many hours of playing around. I found out that setting EVERY app to "launchwithrecent" except from our own app allow us to reboot properly on crashes and keep the navigation in between apps active. There is only one catch! all the other apps need to be already launched to be able to switch. I feel like there is a mixed up in the "launch" vs "launchwithrecent" on first launches vs subsequent launches..<..
FINALLY, I removed the lockdown and tried all of the launches and switching actions on the regular OS... everything works just like I would expect... I don't know why when it come to the lockdown, everything get scrambled.
