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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment