Search Issue Tracker
Fixed in 5.3.3
Votes
0
Found in
5.3.1p1
Issue ID
768929
Regression
No
[UWP][WSA] Locking/unlocking screen causes application ignore mouse input (enabling IIS makes input work)
When UWP or WSA application is running, locking and unlocking screen causes application ignore mouse input. Enabling Independent Input Source makes input work normally.
Reproducible on 5.3.1, 5.3.2, 5.4.0b6.
Repro steps:
1. open "ColorClickerSample.zip".
2. build to UWP or WSA without Independent Input Source option enabled.
3. build and run project on PC.
4. when applications starts, press button few times. Now lock the screen.
5. Unlock the screen, try to press the button again, it doesn't receive any mouse input.
Project built with IIS option enabled makes input work normally.
Expected: input should work without IIS option enabled.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
- Material Component has two horizontal lines under it when its foldouts are closed
- Some selected Mesh Renderer Materials lead to Assets folder when pinged
- Editor colors appear darkened out when HDR Display Output is enabled
Add comment