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.
When using Theme.Material or any of the derivatives on Android, the title of the NavigationPage is not visible, unless you specifically set BarTextColor. If I set the theme of my app to any of the Theme.AppCompat, or @android:style/Theme.Holo, the title displays fine. I am not sure when this started happening, as it used to work fine. The issue popped up when I went to do a build to fix a minor bug in my app.
I have tried to recreate the error in a new app, but when I set the parent of MainTheme to @android:style/Theme.Material, the throws the following exception:
Android.Views.InflateException: Binary XML file line #1: Error inflating class android.support.v7.widget.Toolbar
I also tried to compile using Android 7.1 (Nougat), and get an error on build:
In <declare-styleable> AppBarLayout, unable to find attribute android:keyboardNavigationCluster
I don't believe that's all a coincidence, and think that v8 changed something with the toolbar that caused the title to blank and the other issues.
I noticed when using Theme.AppCompat in my app, that the title bar for the NavigationPage does not display at all.
I'm not able to reproduce the issues you're reporting here. Please provide a sample project that demonstrates it and reopen the issue for us to investigate.
Tested with 188.8.131.52635