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.
Created attachment 14870 [details]
Step to reproduce:
1. Clone the repository: https://github.com/lassana/xf-bug
2. Run the application.
3. Press "Show menu on current page" button.
4. Press "Open second screen" button.
I am unable to reproduce this using the provided repository and Forms version 188.8.131.5205. Please reopen if you manage to have a more specific cause for the crash, but given the log I don't believe it has to do with Forms.
I'm pretty sure that the problem exist because I'm getting crash always when I'm doing this:
1. Run the application (e.g. on simulator iPad 2 iOS 9.1).
2. Go to "Page A".
3. Press "Show menu (Master) on current page" button.
4. Press "Open Page B" button.
There is a video of crash: https://raw.githubusercontent.com/lassana/xf-bug/master/video.mov
I don't know the bug is Xamarin.Forms problem or not, but the sample app doesn't contain any iOS-specific code.
I am a similar bug on UWP
Using a MasterDetailPage as anything other than the root page on an iPad is not supported due to platform limitations within UIKit.
Are there any references to the Apple docs?
what about uwp !
Created attachment 16560 [details]
Since this bug was closed, I removed the original repository. If you need it, you can find it in attachments.
Hope someone will fix the problem someday; nevertheless the similar Android bug #40333 was fixed.