Next time that ever happens have something like `adb logcat | tee log.txt` running in the background so you can actually figure out what's crashing.
My old Android phone has gotten into a very sorry state, I badly need to factory reset it to fix it (eh, and maybe root it while I'm at it) once I get some data off of it - but the other day my bank app happened to be crashing, and I was able to determine it was because Chrome's WebView hadn't updated correctly. So (the Play Store has completely wedged itself and the app has disappeared, seemingly a catastrophically failed update) I grabbed an updated WebView APK from Ze Internetz, and yay, fixed.
Although yeah, I can't really recommend that particular strategy as a particularly secure first-class solution...
But watching logcat can be very useful. And you can at least wave the log info above your head like an annoying "I did my due dilligence" flag :P
Comments
Next time that ever happens have something like `adb logcat | tee log.txt` running in the background so you can actually figure out what's crashing.
My old Android phone has gotten into a very sorry state, I badly need to factory reset it to fix it (eh, and maybe root it while I'm at it) once I get some data off of it - but the other day my bank app happened to be crashing, and I was able to determine it was because Chrome's WebView hadn't updated correctly. So (the Play Store has completely wedged itself and the app has disappeared, seemingly a catastrophically failed update) I grabbed an updated WebView APK from Ze Internetz, and yay, fixed.
Although yeah, I can't really recommend that particular strategy as a particularly secure first-class solution...
But watching logcat can be very useful. And you can at least wave the log info above your head like an annoying "I did my due dilligence" flag :P