search

Rifluxyss / acra

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

Relaunching crashed app from home key recent app shortcut displays crash report dialog again #6

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Application configured with notification dialog crashes
2. Respond to the notification, fill in crash report dialog, and click OK
3. Long press home button and select the application icon to launch it again

What is the expected output? What do you see instead?
I expected the application to launch. Instead, the crash report dialog appears. 
 Also, the application name shows as org.acra.CrashReport... (probably 
truncated CrashReportingDialog)

What version of the product are you using? On what operating system?
ACRA 2.0.3, Droid with 2.1

Please provide any additional information below.
An option to directly open the permission dialog without first going through a 
notification would be quite desirable.

Original issue reported on code.google.com by marshgos...@gmail.com on 9 Jul 2010 at 2:47

GoogleCodeExporter commented 8 years ago 
I will investigate this case to avoid the display of the dialog on application 
resume.

Regarding direct dialog display on crash, I think it's not technicaly possible. 
I've tried to work this around and never have been able to open a new dialog 
while crashing. It looks like the application process is in a special state 
where it is unable to create new UI elements. The native android crash dialog 
is started from a system process which is different from the app, and is 
running in its own application process.

Thanks for reporting the issue.

Original comment by kevin.gaudin on 9 Jul 2010 at 3:26

GoogleCodeExporter commented 8 years ago 
Will update the wiki page, setting android:excludeFromRecents and 
android:finishOnTaskLaunch to true should solve the issue.

Original comment by kevin.gaudin on 21 Aug 2010 at 3:01

GoogleCodeExporter commented 8 years ago 
To be tested.

Original comment by kevin.gaudin on 21 Aug 2010 at 3:23

GoogleCodeExporter commented 8 years ago 
Don't use android:finishOnTaskLaunch="true", this prevents the Crash Dialog 
from opening... :-(

Original comment by kevin.gaudin on 21 Aug 2010 at 3:39

GoogleCodeExporter commented 8 years ago 
android:finishOnTaskLaunch="true" is good, the Crash Dialog not opening was 
because of fresh modifications to the dialog code... Sorry for the noise here 
;-)

Original comment by kevin.gaudin on 21 Aug 2010 at 4:06

GoogleCodeExporter commented 8 years ago

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