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 try to push a modal page onto MainPage without an animation before MainPage is ever shown then MainPage still sometimes appears to the user. I.e., this code is in the app's constructor:
MainPage = MyPage();
MainPage.Navigation.PushModalAsync(new ContentPage(), false);
With that code, sometimes MainPage shows up to the user before the modal page. That should not happen. The purpose of the non-animated APIs is to be able to do things like this without the user seeing the intermediate state.
To reproduce, run the attached project. Sometimes (it doesn't seem to happen the first time after building, possibly due to first launch simulator differences or something) you can see the ListView before the blank page.
Created attachment 10895 [details]
I am seeing this exact same issue with/without animations. Just a note that the output log has this warning when it occurs:
Warning: Attempt to present <Xamarin_Forms_Platform_iOS_ModalWrapper: 0x1647b8c0> on <Xamarin_Forms_Platform_iOS_PlatformRenderer: 0x16117c80> whose view is not in the window hierarchy!
Created attachment 19482 [details]
Updated repro (126.96.36.199)
I've been trying to reproduce this behavior with 188.8.131.52, and it appears to have been fixed.
I can confirm that the issue no longer exists.