Skip to content
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

Application starts with error notification #16

Closed
GoogleCodeExporter opened this issue Apr 7, 2016 · 12 comments
Closed

Application starts with error notification #16

GoogleCodeExporter opened this issue Apr 7, 2016 · 12 comments

Comments

@GoogleCodeExporter
Copy link

Acra 3.0.0

Setup for email notifications. An error occurs, users ignores error 
notification.

On next launch of the app, the error notification pops up but there is no 
notification to click on to actually send the error data.

I submitted this error already for the previous version.

Original issue reported on code.google.com by martin.h...@gmail.com on 27 Nov 2010 at 5:34

@GoogleCodeExporter
Copy link
Author

I can't manage to reproduce the issue with my simple test app. Do you have a 
sample application code to provide to demonstrate this?

ACRA's test app is an application starting with a stable launcher Activity, 
which has a button to start a new Activity systematically crashing in its 
onCreate() method. Do you think your issue occurs in a different 
error/application topology?

I really would like to fix this but can't understand when it happens.

Original comment by kevin.gaudin on 28 Nov 2010 at 4:26

@GoogleCodeExporter
Copy link
Author

I don't know where your test app is. So I created my own, see attachment.

There are two buttons, one to create an exception, the other to send a silent 
report.
Please add your own form id in ApplicationWrapper before trying.

Hit "silent report". Report is sent.
Hit "crash". Report is send but added user data from silent report is still 
included. Shouldn't that be reset?

Hit "crash". Don't send the report.
Hit "silent report". Both reports are being sent, but the notification remains. 
If the user now sends the report from the notification, nothing is being sent 
and any data that the user added is lost.

Hit "crash". Clear the notification.
Relaunch the app. You get a new notification.

I know these are different errors than originally reported. I will check if I 
do anything wrong in my code that may have caused this.

Original comment by martin.h...@gmail.com on 29 Nov 2010 at 6:51

Attachments:

@GoogleCodeExporter
Copy link
Author

Great, I'll test and fix ASAP.

The third example is not really an issue. In my point of view clearing the 
notification was not an explicit decision regarding the crash report so it was 
natural to notify again on application restart. Moreover, I'm not sure ACRA can 
be notified when the notification is cleared. I'll check this and think about 
it.

Thanks.

Original comment by kevin.gaudin on 30 Nov 2010 at 9:01

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Original comment by kevin.gaudin on 30 Nov 2010 at 9:01

  • Added labels: Milestone-Release3.0.1

@GoogleCodeExporter
Copy link
Author

Ok, I can live with that. Actually I don't think you should do anything about 
it. Instead, you can give the app more power over your library by exposing some 
functionality though:

- public method to delete all saved reports
- public method to delete all saved reports that are silent
- public method to delete all saved reports that are not silent (then the app 
can decide if it want to continuously nag the user until he acknowledges or 
clears a notification)

Original comment by martin.h...@gmail.com on 30 Nov 2010 at 9:16

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Filed Issue 20 for these report purge methods.

Fixed the crash + silent = notification without report issue.

Original comment by kevin.gaudin on 9 Dec 2010 at 11:24

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Thanks Kevin. How can I download and test 3.1.0? I don't see it anywhere.

Original comment by martin.h...@gmail.com on 10 Dec 2010 at 9:26

@GoogleCodeExporter
Copy link
Author

There's no 3.0.1 (bugfixes) nor 3.1.0 (new features) for the moment, I just 
defined these versions as target releases for these issues.

Anyway, I think I'll release only a 3.1.0 version with both bugfixes and new 
API features as both API features requested (reports purge + more actions on 
custom data) won't have much impact on the core code.

Original comment by kevin.gaudin on 11 Dec 2010 at 12:29

@GoogleCodeExporter
Copy link
Author

Sounds like a plan. When you have 3.1.0 ready, I will be happy to resume 
testing.

Original comment by martin.h...@gmail.com on 11 Dec 2010 at 7:09

@GoogleCodeExporter
Copy link
Author

Original comment by kevin.gaudin on 22 Dec 2011 at 9:06

  • Changed state: Verified

@GoogleCodeExporter
Copy link
Author

I have been using the v4 for a while and I didn't have any issues. Thanks.

Original comment by martin.h...@gmail.com on 22 Dec 2011 at 9:29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant