When deployed to an Android device, when the user presses the “Home” or “Back” buttons to leave the game, and then later runs the game again, the game resumes where it was instead of starting over. The end user has no way to actually quit the app. I guess this is part of how Unity handles the Activity life cycle in Android with its implementation of things like onPause, etc., and I can see how this might be what some games want sometimes, but we already handle save/load game when we need it without this “forever alive” approach. Since we publish to multiple platforms, I would hate to have to put a new “quit” button on every screen for Android only (and this would also be a bad user experience, possibly even bad for battery life, etc.) Is this something we can control from within Unity yet? Is this something I’ve set stupidly in my Unity project or is this what everyone sees?
Thanks for any insight, and I am still absolutely loving the Android support in spite of small issues like this. It’s amazing how much does work flawlessly.
