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 14549 [details]
This one is an interesting one.
Open up the App on a new Page in a NavigationPage.
From that page change the MainPage to a new NavigationPage with a default ContentPage then immediately navigate to another page.
Then from this TabbedPage navigate to a new page, then go back and it will crash.
Attached is a repro. Start it up.
Press Move (it will go to the TabbedPage)
Press Move Again (it will go to a ContentPage)
Then press Back * It will now crash with Element already a child of another element.
If you navigate to each page by letting each page load first and pressing a button on the page to move to the next one it all works ok.
To me it seems like because the OnAppearing() is not running or something is not running on page because it is just quickly added to the stack but never visible.
Fixed as of 126.96.36.19905