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.
Xamarin Studio 5.9.7
Xamarin Forms 126.96.36.19971
List views on devices running Android M appear to have extra padding surrounding the list view content. Here's a video that displays the problem:
I've attached a Xamarin project that recreates the issue when running on an Android device on M.
We are having the same issue here. Tested on my Nexus 5 running Android 6.0
Created attachment 13481 [details]
Xamarin project that reproduces the issue
For this attachment:
- Unzip, open in Xamarin, restore project
- Launch on a device/emulator running Android M
- Scroll the listview to see the header/footer padding
I have this bug since July:
And it still exists on the latest xamarin forms release.
Xamarin Forms: 188.8.131.5271
Just to clarify a bit more on this issue:
If I choose to compile targeting a lower Android API (22 or below), this bug does not exist on M devices. Additionally, this issue does not seem to exist while using an older version of forms (184.108.40.20623), even if targeting api 23.
Also, I would recommend explicitly setting an override API version for "Target Android version" if attempting to reproduce/work through this issue. "Automatic - use target framework" caused some headaches.
Any update on this bug? It makes our app quite unusable and is really annoying...
No worries, we are looking into it
Should be fixed in 1.5.2-pre2
*** Bug 35863 has been marked as a duplicate of this bug. ***
Any update on this issue.