Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Programs sometimes need to save the state of the navigation stack when the program is suspended and terminated, and restore the stack when the program starts up again. However, there is a problem restoring multiple nested modal pages on iOS.
A general-purpose solution to the problem of saving and restoring the navigation stack is this Application derivative:
That class is demonstrated by this program:
This program allows navigating to an arbitrary number of modeless or modal pages, clicking a Stepper on each page for some data to identify the page, and then terminating the program.
To see the iOS problem, first remove a hack from MultiPageRestoreableApp that "fixes" the problem:
This hack inserts a Task.Delay(100) call after each call to PushModalAsync.
Now run the program under iOS. Navigate to at least two modal pages. Use the Stepper to identify each page. Terminate the program from the phone or phone emulator so the state is saved. Run the program again. The page stack is not properly restored.
Hey Charles :)
Thank you for taking the time to submit this feature request. We like this idea and have added it to our internal feature tracking system.
Xamarin Forms Team