I’m nearing the end of a development cycle and have a relatively bug free version of an app I’d like to release. I’m madly testing on various devices I have access to, but there are still a few corner cases that cause a crash. I hope to fix them before I ship, but I doubt I’ll find them ALL given my limited testing resources.
The problem is, things can get really ugly when an app crashes but doesn’t exit. The worst case I can foresee is a user continuing to use the crashed app until he/she notices that something isn’t quite right then reports the “problem” which really isn’t the problem at all but more of a symptom of a post-crash app going all Frankenstein. If I’m lucky they just leave a bad rating, but if I’m unlucky they’ll email or post about the problem which will lead me down the wrong path.
I want to avoid this case by being able to detect that the app has actually crashed and simply close it. I’d rather have the app appear to crash to the desktop than have it keep on running in a defective state.
I looked through tutorials and forum posts but didn’t find anything that looked like a solution. If an app throws an error it seems like I should be able to detect it and just close the app. Is there a way to do this? [import]uid: 9422 topic_id: 33933 reply_id: 333933[/import]