Bug 16037 - Crashed Xamarin.Android Applications no longer Restart Properly
Summary: Crashed Xamarin.Android Applications no longer Restart Properly
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.10.1
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2013-11-08 06:16 UTC by bryan costanich
Modified: 2017-06-29 03:27 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Repro Solution - see "HandlingCrashes" app in it. (436.31 KB, application/zip)
2013-11-08 06:16 UTC, bryan costanich

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description bryan costanich 2013-11-08 06:16:12 UTC
Created attachment 5369 [details]
Repro Solution - see "HandlingCrashes" app in it.

It used to be, that when a Xamarin.Android application crashed, it would try and restart the penultimate activity, then if that crashed, it would go back one, etc. Until it hit a certain threshold, and then wouldn't try and restart, and you'd have to manually restart.

Now, however, it appears something has changed, and Xamarin.Android applications are essentially non-restartable. At first, I thought this was just a Jelly Bean feature (as i was testing it on a galaxy note), but i created an Ice Cream Emulator, and found that it actually happens there as well, and I know that it used to work fine on Ice Cream Sandwich.

I suspect something is happening with the Mono Runtime here, in that the application is not actually restartable, due to some non-reconstructable state of the VM after it's been torn down.

I've attached a repro. Open the attached solution, and run the HandlingCrashes project, navigate through to the crash screen and click either one of the crash buttons to cause a crash. Note that it tries to restart the penultimate (intermediate screen), but it appears, from the log output, that that screen isn't even launching, and instead that is like a bitmap cache of the screen. it then immediately just drops back down to the home screen of android.
Comment 1 Chris Hardy [MSFT] 2017-06-29 03:27:30 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.