I made some changes to your exception handler so that the user will
see the standard force close dialog on unhandled exceptions. What I
am doing is getting the default android handler and passing it to the
your default handler so that it can call the android handler after it
is done. This is
Oops not finished.
I made these changes in the Thread run method.
// Get android default exceptions handler
Thread.UncaughtExceptionHandler orgHandler =
Thread.getDefaultUncaughtExceptionHandler();
// Register default exceptions handler
1) When an exception occurs, the application will just drop back to the home
screen and the user won't actually know that an exception has occured.
Any luck on sorting this out? A dialog that informs the user of the
error and a report this problem button that opens the email app
would be
Well, I am using a workaround currently, which means that the application
will restart. On application restart a dialog will then notify the user that
a problem has occurred.
The problem here is that I cannot get a context in the default exception
handler (where I dump the stack trace) and thus I
Okay, I have started out with a very simple and not at all streamlined
implementation. Some documentation and a binary can be found here:
http://code.google.com/p/android-remote-stacktrace/
I'll be updating it, as I go along, but if you have anything you want to
add, please let me know.
The idea
I do this in my beta applications and it is incredibly valuable.
I am not aware of any existing implementations, so I built it myself. I'll
store the stacktraces on the phone and upload them to a webserver, where I
have a PHP script which will store the stack trace to a plain text file and
also
Mads,
Thats exactly what we all need.
How do you get unhandled exceptions or do you put try...catch in all
your code blocks?
Do you submit stack traces individually or batch them up?
Any chance of sharing some of the code?
We really need a generic component for this - it will be a huge boost
Yes, you are right. It could probably be helpful to others and I'd be happy
to share - I'll see if I can create a component somehow over the weekend. I
don't have the code with me right now, but I'll be back ;)
Basically I just have a default exception handler, which will catch all
unhandled
That would be really great if you could post something Mads.
Alex
On Mar 5, 11:50 am, Mads Kristiansen mads.kristian...@nullwire.com
wrote:
Yes, you are right. It could probably be helpful to others and I'd be happy
to share - I'll see if I can create a component somehow over the weekend. I
9 matches
Mail list logo
