As shown in the image, when updating Xamarin forms from the latest 2.3.3 version to the first 2.3.4 version, the statusbar overlaps the navigation bar. This behaviour ist still there in current version 2.4.0.38779. No code was changed between those both images despite the Xamarin.Forms update.
I use a MasterDetailPage, where the detail part contains a navigation page with a ContentPage inside. No custom stuff, just the default pages.
I cannot find any issues relating this nor any breaking changes documented explaining this change in behaviour.
For me it seems the correct display is the variant in version <2.3.4. Or is the new display correct and I have to set some flag to pull the navigation bar beneath the statusbar?
PS: I use Prism.Forms as framework.
UPDATE: Problem is solved in Xamarin 3
ORIGINAL:
To answer my own question:
Unfortunately this is not possible at the moment:
There is a pull request regarding the issue: PR
And a renewed Pull request:
https://github.com/xamarin/Xamarin.Forms/pull/1287
The bug report: Bugzilla
Thread from BjornB who suggested the PR: Xamarin Forum
Related
I have a working project written with angular nativescript, and now i want to add some tabs using 'BottomNavigation'. I looked in the documentation and it seemed pretty simple, but when i added the code to my project all of the tabs just overlayed on each other and i didn't saw any tabs, as if i just put the pages one on another. What am i missing? What should i do in order to use bottom navigation? I tried to create a new helloe world project and just add the bottom navigation but i got the same result. However, when i created a 'tabs' project it did had proper tabs.
I suspect its have somthing to do with the {N} version. I recently updated to the latest version (8.1.5) and there are a lot of troubles with it. Does bottom navigation still supported on this version? How can i make it work?
Well, i found the solution. In case someone in the future will face the same problem:
It is a version problem. Since version 8 you should add the package manualy as described here:
https://github.com/nativescript-community/ui-material-components/tree/master/packages/bottom-navigation#installation
I'm aware that when developing in Xamarin.Forms I have available some tools for hot reloading, such as:
https://github.com/AndreiMisiukevich/HotReload
https://marketplace.visualstudio.com/items?itemName=Xamarin.XamarinLiveReload
https://www.livexaml.com/
However I wasn't able to find an equivalent alternative for Xamarin.Android. Is there an alternative out there that I can use for hot reloading on Xamarin.Android?
There's two ways of creating a layout in Xamarin Android:
Using axml layouts - If you upgrade to the latest Xamarin & Visual Studio on a Mac, you will notice that the designer view for a layout gets updated in real time with the axml code. So technically it's live reloading.
Inside the fragment(CS file) - For this you can use Continuous, as you can see it in use here. Ryan Davis is available on Twitter, and he's pretty quick to respond
I am working on an instant app demo app. I used the default template which I extended with a RecyclerView and a custom adapter. My problem is that my layout is totally broken:
As you see the toolbar is the same, but something does not work correctly regarding the coordinator layout. The floating action button is missing and the navigation drawer is not displayed below the system UI (the notification area) and yep of cause the menu is empty.
The both screens are debug builds so proguard is not messing anything up (I got also release working with proguard, but of cause I still have the same issue). On the left is the result of the gradle task :app:assembleDebug and on the right :instantapp:assembleDebug.
Since I use except of the recycler view the default template for this app I add no code, any idea why my layout is broken in instant apps?
Please follow these steps and you should be good to go!
https://developer.android.com/topic/instant-apps/getting-started/first-instant-app.html
Note : Please select Navigation Drawer Activity in Step 8
From the shared image, it looks like you have modified some code from the default Navigation Drawer Activity for your IA. If yes, please share the code to investigate.
Also, let me know the device/emulator and the Android studio you are using. I was not able to reproduce the issue with Studio version 3.0.1 on Nexus 5x (Android version 8.0.1). Following is the image of the instant app from my nexus 5x with 8.0.1 build. Let me know if I am missing something!
I have a problem when using Xamarin.Forms in conjunction with Prism.Forms (Unity) on an Android 5.1.1 (Lollipop) device.
Specifically, if I navigate to/from forms with "animation: true" those forms do not always work correctly afterward - specifically, the forms are not always updated in response to a PropertyChanged event. The forms work perfectly on Android 6.0 and 7.1 (the only other devices I have available for testing).
If I change all of my calls to INavigationService.NavigateAsync so that "animation" is false, those forms behave properly as long as I do not use the hardware "back" button to exit a form (as this then animates again). I have even created an override of the "UnityPageNavigationService" that overrides the "animated" parameter on calls to "DoPop", "DoPush" and "GoBackAsync" (I am pretty sure that the NavigateAsync method eventually calls one of these for all requirements except in the case of changing the content of a MasterDetailPage).
I am pretty sure that this is a Xamarin problem and not a Prism
problem as having looked through the code on GitHub it appears to me
that the Prism INavigationService implementation eventually comes back
to the Page.Navigation.PushAsync(...) etc. methods and I am also
pretty sure that the Prism navigation service is not intercepting the
back button and interacting with it.
Is there any way to disable the animations when navigation is
instigated by the hardware back button?
Is there a way to override the INavigation implementation for a platform (obviously Android in this instance)?
Is there a known issue and/or work-around here for Xamarin Forms on
Lollipop 5.1.1?
I am using Xamarin Forms 2.3.4.231, Prism.Forms 6.3 and Prism.Unity.Forms 6.3.
I eventually resolved this and it was nothing to do with Prism Navigation nor Xamarin.Forms but was instead caused by the element of the AndroidManifest.xml not being the first child of the element.
I had sorted the children of the element alphabetically making the last element and this broke it (though not on later versions of Android).
On Android 2.x, I cannot get Bootstrap modals to work. They open properly, but then they will not scroll if they are larger than the screen. And you can't click on any of the buttons to close the dialog. Basically, it opens and displays properly, but is completely dead in the water in terms of interacting with the modal.
Bootstrap has no interest in fixing it as they don't support older Android versions. But, I thought there simply HAS to be a way to make it work, right? But apparently not.
I have tried the following hacks, and none of them work. They're all at least a year old, so perhaps they applied to Bootstrap 2.x, but they aren't working for Bootstrap 3.
https://github.com/twbs/bootstrap/issues/8975#issuecomment-24804826
https://github.com/twbs/bootstrap/issues/9890#issuecomment-22915234
https://github.com/twbs/bootstrap/issues/5589#issuecomment-9745069
https://github.com/twbs/bootstrap/issues/3230#issuecomment-5629022
And so on...
Does anyone out there have a solution? Or do I have to use a different modal component? I'm required to support all versions of Android for this project, regretfully.