I have a problem in an application that occurs after the application is destroyed while in the background. While I have some fixes in place, I want to be able to test them immediately.
If I background my application and do a "force stop" from system settings on the app, this doesn't seem to recreate the issue when I then resume the app.
Right now, I have to background the application and wait nearly 12 hours before trying it again.
How can I tell android to destroy the application so that I can test my fixes without waiting around.
There is an option in new versions of Android in Settings>Developer Options called Don't Keep activities which will destroy every activity as soon as the user leaves it. Not sure if this does a force stop or not, but worth looking at.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With