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 Forms version: 184.108.40.206
Android works as expected. iOS not refreshing ItemSource after update.
Click "Write Tab"
Click "Write" Button a few times
Go back to the "Log" Tab. The listview should display items.
Created attachment 18250 [details]
The workaround is to add this:
list.ItemsSource = null; // first set to null. should not be needed
list.ItemsSource = App.Log;
I'm not sure why this was confirmed. Was this regression?
The issue is that App.Log is not changing its reference but its content. List<string> has no concept of individual items updating. Use an ObservableCollection instead.
public static ObservableCollection<string> Log;
Actually, since you said Android works, then this is probably a bug. I'll try to look at it again tomorrow.
I was doing a test and expected it to update like Android without first setting listview.Itemsource = null. I just rebound it on appear.
@Andrew, this does not work for me on AppCompat either. You said it's working on Android, but I can't duplicate it. Perhaps, try uploading a screencast showing us it's working on Android.
As I said earlier, you should use ObservableCollection instead which implements INotifyCollectionChanged and INotifyPropertyChanged.
This is not a bug. Using an ObservableCollection lets it function as expected.