Search Issue Tracker
Won't Fix
Votes
6
Found in
2019.1.0a3
Issue ID
1087313
Regression
No
[iOS] CoreMotion errors on any project launched on iPhone XS/XS Max
Steps to reproduce:
1. Open attached project (or create an empty one)
2. Build for iOS
3. Deploy to iPhone XS or iPhone XS Max
4. Notice couple of errors at the startup:
Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 1203, TID: 867800, Thread name: com.apple.CoreMotion.MotionThread, Queue name: com.apple.root.default-qos.overcommit, QoS: 0
Reproduced with: 2018.3.0b3, 2019.1.0a3
Tested with:
iPhone XS (iOS 12.0) - Reproduced
iPhone XS Max (iOS 12.0) - Reproduced
iPhone X (iOS 12.0) - Not reproduced
Comments (1)
-
mml
Apr 29, 2019 08:27
This also happens with a freshly created empty project using
Unity 2018.2.21f1,
Xcode 10.2.1 (10E1001) ,
11-inch iPad Pro
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
- Object Selector becomes unresponsive when selecting root UI Document as Data Source for Add Binding in UI Builder
- Search #Light.m_Shadows.m_Type query block does not detect default Light objects in Scene unless they were modified
- Shader Graph "Create Node" menu has a doubled text in search when the text was deleted replaced to the space and then the exact same text was entered
- Multiple non interactable Worker Processes are active when calling undelayed editor processes in the InitializeOnLoadMethod
- Rotate tool rotates to incorrect values when enabling snapping while rotating in Global Tool Handle
Resolution Note (2019.1.X):
Seem like an internal issue in CoreMotion initialization, this happens in the framework itself so there isn't much we can do about it.