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.
I've been noticing this issue on Android for some time, since 1.3.5. We have a custom Cell (we call it ExtendedCell), its renderer is only implementing/overriding the GetCellCore method. In this method, the custom cell layout is inflated from XML, and the values are set for specific fields.
It works fine on regular ListViews, but as soon as Grouping is enabled, it goes hijinks. Any time there's a scroll event, the graphics in these elements are overridden by the headers themselves - but only the graphics. It includes all, the whole view (please see attached screenshots)
Created attachment 10857 [details]
Screenshot of the issue
We'd be happy to help you resolve this issue. Please help us by attaching a reduced reproduction to the bug by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue. If you'd do this for us we would very much appreciate it.
Xamarin Forms Team
Found the issue.
Initially I was inflating the layout within the GetCellCore, and assigned the various properties there (by FindViewById, etc.).
Now, if I extract that to a separate class, where the constructor initializes the layout, and I assign all views I use to properties, it works fine.
Thank you for your bug report. We are assuming that this problem has been resolved, and we are closing this report.
Xamarin Forms Team