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
-
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
- [Android] The Player freezes when disabling Bluetooth while connected to the headphones
- Addressable bundles are not retrieved from the cache when a WebGL Player is refreshed
- Sprites are incorrectly occluded by Sprite Physics Shape culling when behind in sorting order
- CPU usage is increased when the Editor is idle with the ProBuilder Package installed
- Unstable lighting when additional light sources are added in Shader Graph nodes
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.