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 for Bug 58289 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 23707 [details]
I discovered a situation with Xamarin Forms and iOS I feel is not ideal:
Example project pushes three modal views shortly after each other with the following results:
-> ModalPushing is called three times, ModalPushed only two times
-> there are three DIFFERENT views in the modal stack
-> there are three views displayed on the iPad, but the second and third view are IDENTICAL
-> if you manually pop the top view you see the identical view below it (so there are three views displayed and not only two but ModalPushed is never called a third time)
-> if you try to pop the top view with an awaited PopModalAsync any code after it won't be executed, if you pop it without await code after it is executed
I know that in this example project I could just easily await the PushModalAsync, but I discovered the situation in a different context and I feel that situation should never occur at all.
I don't believe this is necessarily an iOS exclusive issue, but it at least occurs with the nightly build as well.