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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment