09-26-2009 12:58 PM
I have an Application (not UiApplication) that's an auto-start system module, it's a simple options provider and PhoneListener. It autostarts after install or reinstall, always autostarts after reboot on my 8330, but on at least some Storms, doesn't autostart after the 1st or 2nd reboot. If it's reinstalled it's back.
If an unhandled exception occurred the user should be getting an error popup, right? And none of the handled exceptions would result in a termination, just missing functionality.
I can't reproduce this on my 8330 plugged into the debugger, have no real Storm to test on, and it's fine on the Storm simulator after simulated resets. So I have to guess what may be happening. Doesn't seem like an exception, so what would cause a non-UI application to drop out of the event dispatcher right away at startup?
Any ideas about this are appreciated.
09-26-2009 02:19 PM
Not sure that it matters, but could you ask you customer (or whoever is this person with Storm) what is the way they use for reset?
If user with Storm plug battery out and then in, does your application auto-start?
09-26-2009 09:46 PM
it depends on how you handled the exception. in your code, do you display a dialog alert if it caught an exception?
and maybe, just maybe your application might be holding the main event thread for a long time like processing something in it which makes the JVM think that your application is not responding causing it to shutdown your application.
09-28-2009 06:47 AM
Ask the user to send you the Event Log. It'll probably contain an "interesting" exception. If that's the case, ask the user to open the entry corresponding to the exception and send it to you too.
P.S. If it's just an options provider, why do you even need to enter the event dispatcher? (Haven't written any options providers, but it sounds like an auto-start-and-just-register-something app that simply exits after registering an options provider)