Closed GoogleCodeExporter closed 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
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
To be tested.
Original comment by kevin.gaudin
on 21 Aug 2010 at 3:23
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
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
Original comment by kevin.gaudin
on 11 Dec 2010 at 12:32
Original issue reported on code.google.com by
marshgos...@gmail.com
on 9 Jul 2010 at 2:47