Search Issue Tracker
Fixed
Fixed in 2021.3.40f1, 2022.3.34f1
Votes
2
Found in
2021.3.39f1
2022.3.32f1
Issue ID
UUM-73469
Regression
No
[Android] LocationService stuck Initializing with new InputSystem
1. What happened
When Active Input Handling is set to Input System Package (new), Input.location.status remains stuck in the 'Initializing' state and never starts. The only way around this seems to be setting Active Input Handling back to 'Both.'
2. How can we reproduce it using the example you attached
- Build the project attached to Android
- Input.location.status is checked each frame. When set to New, Input.location.status will be stuck in Initializing. When set to Both, Input.location.status will reach the Running/Stopped state.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Add comment