That is very handy for bug-processing. But Dianne's answer is better :=) Fix the issue that throws the exception causing the thread to exit and the activity for force-close. Or handle the exception by catching and dealing with it.
On Aug 28, 1:55 am, dweebo <[email protected]> wrote: > I was looking to do the same thing, or rather to log the stacktraces > remotely for later debugging. > Seehttp://code.google.com/p/android-remote-stacktrace/for how > someone else handled it, works great! > > You could modify their code to suppress android's force close dialog, > I think you just have to not call the default exception handler at the > end of DefaultExceptionHandler. > -Peter > > On Aug 1, 11:30 pm, "[email protected]" <[email protected]> wrote: > > > > > Hi, > > I started a background service process...however, when there is an > > uncaught java exception in one of the threads in that background > > service process, a Force Close dialog pops up oo the screen saying > > "Application XXX stopped unexpectly". My question is, why a thread in > > background service process can cause this Force Close dialog ? where > > is the code to draw that dialog ? Can I suppress the android platform > > to do that....how ? this is annoying as the background process will > > restart itself....and I do not want this type of window to destroy the > > UI. > > > Thanks,- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
