Currently, when the app crashes due to a bug, the app is closed and the user is returned to their Home Screen.
Since this is an accessibility app, this presents a problem as the user may not be able to re-open the app easily. We would like to handle this situation so that when the app enters an unexpected state, the user is not booted from the app.
The following quote sums up a good approach if possible: "I'm thinking more like we do crash, but we figure out a way to restart the app in a crash scenario" -Paul
ProcessPhoenix combined with a global exception handler seems like it would do the trick.
If this works, be careful around the infinite restarts situation!
only time this line in an app makes sense :smile:
Runtime.getRuntime().exit(0); // Kill kill kill!
If you all do put it into a global process handler I would pass in the crash # and time of last crash and don’t restart if it’s been > 3 within the last 10 seconds or something like that. Infinite crashes and restarts would be bad
Currently, when the app crashes due to a bug, the app is closed and the user is returned to their Home Screen.
Since this is an accessibility app, this presents a problem as the user may not be able to re-open the app easily. We would like to handle this situation so that when the app enters an unexpected state, the user is not booted from the app.
The following quote sums up a good approach if possible: "I'm thinking more like we do crash, but we figure out a way to restart the app in a crash scenario" -Paul
Possible solution: ProcessPhoenix
ProcessPhoenix combined with a global exception handler seems like it would do the trick.
If this works, be careful around the infinite restarts situation!