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
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Add comment