Bug 60204 - Bug when running UWP app in assigned access mode
Summary: Bug when running UWP app in assigned access mode
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.4.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Paul DiPietro [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2017-10-16 13:40 UTC by Kristoffer Gjone
Modified: 2018-01-11 12:13 UTC (History)
4 users (show)

Tags: assigned access, kiosk, uwp, fr
Is this bug a regression?: ---
Last known good build:

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:
Status:
RESOLVED FIXED

Description Kristoffer Gjone 2017-10-16 13:40:27 UTC
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:
https://forums.xamarin.com/discussion/94174/crash-calling-displayalert-when-using-windows-assigned-access
Comment 1 Paul DiPietro [MSFT] 2017-10-16 17:03:40 UTC
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?
Comment 2 Kristoffer Gjone 2017-10-17 07:17:08 UTC
Hi. I am currently running Xamarin Forms 2.4.0.282 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.
Comment 3 Richard Poulter 2017-11-30 15:47:40 UTC
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 2.4.0.38779) have made no improvement. Unfortunately, due to an issue with ListView on UWP we've had to revert to Forms 2.3.4.270 at present.
Comment 4 Paul DiPietro [MSFT] 2018-01-08 22:12:02 UTC
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
Comment 5 Richard Poulter 2018-01-09 15:10:15 UTC
Thanks - Looking forward to seeing this in a stable release.
Comment 6 Rui Marinho 2018-01-11 12:13:13 UTC
Should be fixed on 2.6.0-pre1