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 dwe...@gmail.com wrote:
I was
I was looking to do the same thing, or rather to log the stacktraces
remotely for later debugging.
See http://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
Your application has a bug causing it to crash, and the system is dealing
with it. If you don't want this to happen, fix the bug that is causing the
exception to be thrown without being caught.
On Sat, Aug 1, 2009 at 8:30 PM, life0...@gmail.com life0...@gmail.comwrote:
Hi,
I started a
3 matches
Mail list logo
