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.
The same ReactiveCommand can't be executed during execution, so when it starts execution it raises ICommand.CanExecuteChanged and ReactiveCommand.CanExecute() will return false.
If ReactiveCommand is set to ListView.RefreshCommand and when it executes it sets ListView.IsPullToRefreshEnabled to false internally, which removes UIRefreshControl without calling UIRefreshControl.EndRefreshing().
It would be better not to change IsPullToRefreshEnabled until IsRefreshing is set to false. See also 32857
I've filed a new bug which is similar to what you are talking about except it's not specific to ReactiveCommand: https://bugzilla.xamarin.com/show_bug.cgi?id=42330
Also, it does appear the code is calling EndRefreshing (see my notes in #42330). I also expect a different outcome then you mentioned and believe that the control should not be removed based on CanExecute.
For purposes of upkeep I'm going to close this and defer to 42330 since it includes a reproduction and more information to reference while still referring to ReactiveCommand.