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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment