Application starts with error notification

[palpandi]

Application starts with error notification

[GoogleCodeExporter]

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]

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 [email protected] on 29 Nov 2010 at 6:51

Attachments:

• ACRA_Test.tar.gz

[GoogleCodeExporter]

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]

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

• Added labels: Milestone-Release3.0.1

[GoogleCodeExporter]

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 [email protected] on 30 Nov 2010 at 9:16

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

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]

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

Original comment by [email protected] on 10 Dec 2010 at 9:26

[GoogleCodeExporter]

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]

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

Original comment by [email protected] on 11 Dec 2010 at 7:09

[GoogleCodeExporter]

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

• Changed state: Verified

[GoogleCodeExporter]

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

Original comment by [email protected] on 22 Dec 2011 at 9:29