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 59839 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
We've tried to get a custom tabbed page renderer dereived from the TabbedRenderer to utilize the new safe area layout guide. But the base ViewDidLayoutSubview method causes the element and therefore the native view to fill the entire screen.
This method gets called twice during the layout process. In the first call the safe area insets are [44, 0, 34, 0] (that's correct) but in the second call the insets are [0, 0, 0, 0] (filling the entire screen). This results in the custom tabbar overlapping the software home button on the iPhone X since the bottom of the safe area layout guide is equal to the bottom of the screen.
Other renderers probably show a similar behaviour.
A reproduction project to see your custom renderer would always be welcomed here, but we are aware that some changes in general need to be made surrounding the iPhone X and the safe area/notch.