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.
When running my Xamarin Forms UWP app in Windows 10 Assigned Access mode there is a bug that leads to missing updates in my GUI when it is updated through a Call to Device.BeginInvokeOnMainThread. This is done since the update is triggered by a callback from another thread.
I believe the solution might already be found and explained in the following link:
The last comment says that updating resolved the issue. Can you confirm that doing so as well as doing a typical clean/rebuild doesn't help, and possibly provide a reproduction project?
Hi. I am currently running Xamarin Forms 220.127.116.112 and the problem is still present there.
I experience problems when I want to update my GUI from another thread than the main thread. In my case it is from a callback from a "Wifi scan completed event" from Windows. Therefore I wrap my UI update code with Device.BeginInvokeOnMainThread(...). This Works fine in a normal Runtime environment, but when running in Windows 10 assigned access mode it does not work properly since the visible Window is no longer the main window...
I was not involved in the Forum thread, but Attached this merely as a possible solution for you guys.
I've updated the referenced forum thread with more info. The issue returned after Windows 10 Cumulative Update for 2017-09 was installed. Further CUs, Win 10 release 1709 and Forms updates (to 18.104.22.168779) have made no improvement. Unfortunately, due to an issue with ListView on UWP we've had to revert to Forms 22.214.171.1240 at present.
A PR is open for this which uses a check for the assigned access/above lock state: https://github.com/xamarin/Xamarin.Forms/pull/1534
Thanks - Looking forward to seeing this in a stable release.
Should be fixed on 2.6.0-pre1