Bug 24222 - [Android] Unable to hide NavigationBar for MasterDetail page
Summary: [Android] Unable to hide NavigationBar for MasterDetail page
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.3
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-11-03 09:07 UTC by Prashant Cholachagudda
Modified: 2016-03-25 18:08 UTC (History)
6 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Prashant Cholachagudda 2014-11-03 09:07:03 UTC
We can't hide the navigation bar on a MasterDetail page, using NavigationPage.SetHasNavigationBar or using Android Style element
<item name="android:windowNoTitle">true</item>

Using <item name="android:windowNoTitle">true</item> results in a NullReferenceException.
Comment 3 Prashant manu 2014-11-04 01:04:34 UTC
I have checked this issue but not able to reproduce this. To reproduce this issue I have followed the steps mentioned below:

1. Download and open attached test case in XS.
2. Build application and, set android as startup project.
3. Deploy the application on emulator.
4. Observe that you will get the following exception:

I observed that In the bug "NullReferenceException" is described, but I am getting "AndroidRunTimeException".

Could you please let me know that what steps I am missing/wrong to reproduce this issue. Or what steps I have to followed to reproduce this issue ? That will be very helpful to reproduce this issue at our end.

Exception: https://gist.github.com/Rajneesh360Logica/96038a188d8e9b4d92ab

Screencast: http://www.screencast.com/t/Q9tlHZtxLVK 

Application O/P: https://gist.github.com/Rajneesh360Logica/2aab517a48e2c81f916e

Environment Info:

=== Xamarin Studio ===

Version 5.5.3 (build 6)
Installation UUID: 011d70a5-dede-428b-ab04-ef451c2e539d
	Mono 3.10.0 ((detached/e204655)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000023

=== Xamarin.Android ===

Version: 4.18.1 (Business Edition)
Android SDK: /Users/MM/Desktop/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		3.2    (API level 13)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		4.5    (API level 21)
Java SDK: /usr
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Apple Developer Tools ===

Xcode 6.0.1 (6528)
Build 6A317

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 80e9ff7
Build date: 2014-10-22 15:09:12-0400

=== Xamarin.Mac ===

Version: (Business Edition)

=== Build Information ===

Release ID: 505030006
Git revision: fbe3e9453daf6a3bb9a9709ed22bec35f7c9056b
Build date: 2014-10-23 13:08:38-04
Xamarin addins: e44add2b39de4dd57c0742bb2e620dfad84c64c6

=== Operating System ===

Mac OS X 10.9.5
Darwin MacMini.local 13.4.0 Darwin Kernel Version 13.4.0
    Sun Aug 17 19:50:11 PDT 2014
    root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
Comment 4 Jason Smith [MSFT] 2016-03-25 18:08:11 UTC
This should no longer be a problem with the AppCompat backend.