search

kingrukawa / acra

Automatically exported from code.google.com/p/acra
0 stars 0 forks source link

After App crash, App refuses to open and "App has crashed" notification does not bring up dialog to submit crash report. #35

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Make App crash
2. Try to start App again and it tries to start but quickly disappears
3. There is a notification stating the App has crashed. When I click on that 
nothing happens at all.
4. The only way I can get the App to start again is to completely uninstall it 
and then reinstall.

What is the expected output? What do you see instead?
When I was first setting up ACRA and I ran some tests and it worked fine. I 
expect a crash report to pop up and let the user report.

What version of the product are you using? On what operating system?
3.1.0

Please provide any additional information below.
I'm running this test on a HTC Incredible.

Original issue reported on code.google.com by agfis...@gmail.com on 11 Feb 2011 at 5:41

GoogleCodeExporter commented 8 years ago 
Hmmm. I was just thinking about this and have a theory. The error that I was 
replicating to cause this crash was by putting erroneous data into an 
application preference and then running a command that takes that data and uses 
it to create a new profile. When the command is issued to create the new 
profile the crash occurs. Up to here everything is working normally but this is 
where I think the problem lies. When my application restarts it goes into the 
preferences and loads the default settings. Since one of these default settings 
is corrupt and causes a crash, the application just crashes again and I'm never 
able to get the crash reporting dialog up to send a report. It seems that if a 
crash happens early enough in the application there is never an opportunity to 
submit a crash report.

I obviously need to add some input checking/sanitation on my preferences to 
prevent this from happening but I thought I would let you know that there is a 
way to prevent ACRA from sending reports. Maybe some sort of count could be 
added where if the application crashes several times in a row then the reports 
could be deleted or sent anyway (Somehow this decision would have to be given 
to the user, maybe a preference for automatically sending error reports without 
user intervention.)

Original comment by agfis...@gmail.com on 11 Feb 2011 at 5:57

GoogleCodeExporter commented 8 years ago 
I'll think about this. Thanks for reporting.

Original comment by kevin.gaudin on 12 Feb 2011 at 2:07

GoogleCodeExporter commented 8 years ago

Original comment by kevin.gaudin on 12 Feb 2011 at 2:16

GoogleCodeExporter commented 8 years ago 
Same problem here.

Original comment by xdrago...@gmail.com on 2 Sep 2011 at 12:13

GoogleCodeExporter commented 8 years ago 
I ended up adding sanitation of my inputs and preferences and that ended up 
making the ACRA issue become a non-issue.

Original comment by agfis...@gmail.com on 2 Sep 2011 at 12:29

GoogleCodeExporter commented 8 years ago 
Who is kevin guadin and why does he show up as the owner

Original comment by boltazar...@gmail.com on 27 Sep 2013 at 5:11

GoogleCodeExporter commented 8 years ago 
I am Kevin Gaudin and as the creator and the main author of this project, I am 
it's owner.

Please note that ACRA and its backend Acralyzer now live on Github:
http://github.com/acra/acra
http://github.com/acra/acralyzer

Cheers,
Kevin Gaudin

Original comment by kevin.gaudin on 27 Sep 2013 at 7:59