-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Takes long time for crash dialog to appear #73
Comments
It might be caused by the usage of Actvity lifecycle callbacks to remove the latest activity from the stack on recent Android versions because users were experiencing crash loops. In the case of the DIALOG interaction method, we add a new activity to the stack just before killing the app... |
@wintersandroid would you copy here the declaration of the |
This is what I have.. |
Thanks. And could you copy the logcat extract from the moment ACRA catches the exception to when the app is restarted ? |
Now.. My app crashed at startup - something failed in the widget and the dialog appeared, the above report is not for that. I cancelled the dialog.. Then I launched the activity with the test null pointer exception, and it appears like the activity is trying to show then it goes away immediately.. My app implements a widget, which has services e.t.c. running in the background.. |
I downloaded the source and added in some debug statements.. To fix this problem, remove the mDialog.dismiss() from CrashReportDialog.onPause() I have been using android 4.2.2, it seems (and makes sense) that the activity gets an onPause() when the dialog is shown above... |
Does it show any other problem. if you put that fix? |
Ok @wintersandroid, I'll test this tonight. The strange thing is that I can't reproduce the issue with my emulator. But it does make sense ;-) |
Well I was testing on 4.1 and now with a 4.2.2 emulator I could reproduce the issue and the fix works like a charm. |
@KevinGaudin It fixes #78 as well. |
I have tried the 4.5 RC, but the crash dialog is not appearing for quite a long time - in one case it was about 4 hours later.
This is the code i use to initialize it, I have my own report sender (but we don't get there yet, that bit does work after the dialog)..
The text was updated successfully, but these errors were encountered: