Bug 44171 - SearchBar not displaying on Android 7
Summary: SearchBar not displaying on Android 7
Status: RESOLVED DUPLICATE of bug 43975
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 2.3.1
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-09-11 11:39 UTC by Kasper
Modified: 2017-03-06 13:26 UTC (History)
2 users (show)

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

Solution with reproduction of bug (35.46 KB, application/x-gzip)
2016-09-11 11:39 UTC, Kasper

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 Kasper 2016-09-11 11:39:48 UTC
Created attachment 17410 [details]
Solution with reproduction of bug


On Android 7 (as opposed to say Android 6.0.1), a XF.SearchBar embedded in fx a StackLayout together with another expanding element, will not render correctly. Something goes haywire with the size requests and it ends up being invisible.

I have attached a reproduction. Try running on both Android 7 and Android 6.0.1, to see the difference.

As Android 7 is rolling out on Nexus devices, as I type a fix is urgent.
Comment 1 Paul DiPietro [MSFT] 2016-10-03 15:42:19 UTC

*** This bug has been marked as a duplicate of bug 43975 ***