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
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
Add comment