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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment