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.
Created attachment 11740 [details]
Project that demonstrates the bug
On Windows Phone, an ActivityIndicator placed inside a ViewCell inside a TableView does not show when the property bound to IsRunning changes to true.
This only occurs in Windows Phone.
Android and iOS work as expected.
The same ActivityIndicator placed directly inside a StackLayout works fine in Windows Phone.
Windows Phone 8.1 (emulator)
Windows Phone 8.1 (device, Lumia 640)
Windows Phone 10 (emulator)
Xamarin.Forms 184.108.40.20659 Release
Attached "Blank App (Xamarin.Forms Portable)" project from default template reproduces the issue by showing two ActivityIndicators bound to the same view model property (IsBusy) in a StackLayout and in a TableView.
Created attachment 11741 [details]
Screenshot of bug displaying
Could you please include the solution file in your reproduction attachment?
Created attachment 11966 [details]
Demonstration project with solution
Added solution file
Updated to Xamarin Forms 220.127.116.1176 release
Same issue on Windows Phone
Attachment 11966 [details] includes the solution. Thanks.
The demonstration project, if upgraded to Xamarin.Forms 18.104.22.16847, still exhibits the issue.
I can no longer reproduce the issue with Forms 2.3.3.