Bug 43986 - Pull-to-Refresh does not work on iOS after data is refreshed once
Summary: Pull-to-Refresh does not work on iOS after data is refreshed once
Status: RESOLVED DUPLICATE of bug 43214
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.3.2
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-09-04 04:41 UTC by adrianknight89
Modified: 2016-09-06 21:57 UTC (History)
2 users (show)

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

repro (200.94 KB, application/zip)
2016-09-04 04:41 UTC, adrianknight89

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 adrianknight89 2016-09-04 04:41:09 UTC
Created attachment 17326 [details]

iOS Pull-to-Refresh is broken. If you refresh listview data once, you won't be able to refresh it again. Perhaps, bindings are lost after the first refresh. Android does not have this issue.

Steps to produce:

1) Pull down the listview to trigger either RefreshCommand or Refreshing event
2) Data is refreshed
3) Try to refresh data again
4) iOS refresh wheel keeps running

Please see repro.
Comment 1 Samantha Houts [MSFT] 2016-09-06 21:57:39 UTC

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