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
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
- Graphics.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
Add comment