Search Issue Tracker
Won't Fix
Votes
2
Found in
4.6
2017.4
2018.4
2019.2
2019.3
2020.1
Issue ID
1190107
Regression
No
[iOS 13.0] Rotations around Device Y-axis does not work when rotating a Device and using Remote
How to reproduce:
1. Download attached "GyroscopeTest.zip" project and open in Unity
2. Go to Menu bar-> Edit-> Project Settings-> Editor-> Device-> Chose Any iOS Device
3. Download Unity remote 5 to your iPhone and open the app
4. Connect your iPhone device with a USB cable to your computer
5. Enter the Play mode in the Unity Editor
Expected: Scene rotates as you rotate Device
Actual: Scene does not rotate when you rotating Device
Notes:
- This issue happens only on iOS with 13.0 and above version
- This issue does not reproduce on Android (Mono and IL2CPP) and iOS 12.x and lower
Tested with:
- iPhone 7, iOS: 12.3.1 - Not Reproduced
- iPhone 8 Plus, iOS: 12.0 - Not Reproduced
- iPhone X, iOS: 11.3.1 - Not Reproduced
- iPhone XR, iOS: 12.0 - Not Reproduced
- iPad Pro 3rd Gen, iOS: 13.0 - Reproduced
Reproduced on Unity 2017.4.0f1, 2017.4.32f1, 2018.4.8f1, 2019.2.6f1, 2019.3.0b3 and 2020.1.0a4
-
erikhallgren
Jan 31, 2021 15:24
This causes issues for all users wanting to work with gyro on iOS, please fix!
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (2020.1.X):
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.