Search Issue Tracker
Fixed in 1.2.0
Votes
0
Found in [Package]
1.1.0-pre.5
Issue ID
1371204
Regression
Yes
Accelerometer is not working when using Input System 1.1.0-pre.5 or newer
How to reproduce:
1. Open "AccelBug.zip" attached project
2. Go to Build Settings (File>Build Settings)
3. Build for iOS (or Android platform)
4. Open Xcode project and build for a device
5. Move your device to see the accelerometer running
Expected result: Accelerometer is running and showing the result
Actual result: Accelerometer isn't working
Reproducible with: 1.1.0-pre.5, 1.1.1 (2019.4.30f1, 2020.3.19f1, 2021.1.22f1, 2021.2.0b13, 2022.1.0a11)
Not reproducible with: 1.1.0-preview.3 (2019.4.30f1, 2020.3.19f1, 2021.1.22f1, 2021.2.0b13, 2022.1.0a11)
Repro with:
iPhone 12 ,14.1
iPad Pro 12.9, 13.4.1
User tested with:
iPad mini 4, 14.7.1
iPad mini 5, 14.8
iPhone 11, ios 14.8
Samsung Galaxy S9, 10
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 1.2.0):
Fixed in 1.2.0
Resolution Note (fix version 1.2.0):
Fixed in: 2020.3.24f1