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.
If you look at the ModalStack in INavigation it contains the root node of the NavigationStack on android, but is empty on iOS (correct behavior?). This is when no modal has been shown or is showing.
(I can confirm this.)
And if you call PopModalAsync() it sets the modal stack count to zero, no matter what its value at the time the call is made. And that causes any subsequent calls to PushModalAsync to do precisely nothing - no modal form is displayed. (Problem occurs in 1.4.x, not 1.3.x)
This behavior needs to be unified, the thing Phil Morris mentioned is https://bugzilla.xamarin.com/show_bug.cgi?id=28284
I get the same behavior on WinPhone, except that it doesn’t set modal stack count to 0.
Let's get this fixed Xamarin.
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.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d
Xamarin Forms Team
Just to be clear I think this was resolved in 2.2.0