Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Spike] Think about Crash Handling #461

Open
mattttvaughn opened this issue Jan 9, 2024 · 0 comments
Open

[Spike] Think about Crash Handling #461

mattttvaughn opened this issue Jan 9, 2024 · 0 comments

Comments

@mattttvaughn
Copy link
Contributor

mattttvaughn commented Jan 9, 2024

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!

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
@mattttvaughn mattttvaughn added bug Something isn't working and removed bug Something isn't working labels Jan 9, 2024
@lauren-ahart lauren-ahart moved this to Ready to select in Vocable-Android May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready to select
Development

No branches or pull requests

1 participant