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 for Bug 37126 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 14340 [details]
sample project to show ListView binding error
I have a custom ListView that implements a ItemTemplateSelector. Once the ObservalbleCollection is cleared and loaded with new items the Background property stops working randomly.
I have attached a sample project that exhibits this behavior. All it does is load up a collection with ViewModels (randomly assigning color attributes to them) and the ItemTemplateSelector selects the correct template based on the type (for this example there is only one type)
When you run it you'll see that they are all correct but when you tap any button which causes the collection to be cleared and reloaded with new items, some of the bindings are now messed up. It's like the ListView is holding onto some of the previous bindings and not updating them with the new items data.
This exact sample code works perfect on iOS
This bug is holding up the release of our product, please expedite if possible
As I indicated nearly two weeks ago, this defect is holding up the release of our product. I have provided a example the exhibits the bug. What else do I need to do to escalate this defect?
This bug was confirmed a week ago. Please provide status. If it cannot be fixed we need to know now in order to create an alternative design.
Joe- Can you tell me Xamarin's status on addressing this defect? We have a completed product but cannot release it due to this problem. Our client is going more impatient by the day. We really need to know if the time to fix is days or weeks at this point.
@Steve Hatch: I personally have no status on this. Just reporting that I too am experiencing the same issue.