What does Core Motion error 102 mean?

Question

I use Core Motion's sensor fusing to get north oriented motion updates:

[motionManager startDeviceMotionUpdatesUsingReferenceFrame:CMAttitudeReferenceFrameXTrueNorthZVertical toQueue:motionQueue withHandler:motionHandler]

In a very rare case that can be reproduced only on selected customer devices (iPhone 4S running iOS 6.0.2) I receive this error in the motionHandler:

Error Domain=CMErrorDomain Code=102 "The operation couldn’t be completed. (CMErrorDomain error 102.)

Also, it seems I don't get any valid deviceMotion updates after that. Does anybody know what this error 102 means? I can't find anything in the documentation.

Ortwin Gentz · Accepted Answer · 2014-12-23T11:26:31.873

As Krishnabhadra correctly pointed out, this error code means CMErrorTrueNorthNotAvailable. The description ("True north is not available on this device. This usually indicates that the device’s location is not yet available.") unfortunately doesn't give any hint how to solve the issue so I'd like to describe my findings when this error occurs.

It occurs on a tiny (a handful out of many thousands) fraction of iOS 6.0+ devices when using CMAttitudeReferenceFrameXTrueNorthZVertical (CMAttitudeReferenceFrameXMagneticNorthZVertical is OK). Despite the error description, Core Location works correctly. On affected devices the bug is triggered in 100% of the cases and blocks Core Motion updates completely. -[CMMotionManager deviceMotion] always returns nil.

Resetting the iOS system settings fixes the problem.

I’ve logged rdar://12952327 with some more details.

Update: This error occurs if compass calibration is disabled in the privacy / location services / system services section.

The error is very likely due to what Ortwin writes in the **Update**: compass calibration is switched off; thanks for finding that Ortwin! Note also that, even when everything is fine, it is normal that you get this error at least once before the real samples come in. — fishinear, Feb 01 '16 at 14:07

score 3 · Answer 2 · answered Jan 02 '13 at 11:27

3

From documentation

typedef enum {
   CMErrorNULL = 100,
   CMErrorDeviceRequiresMovement,
   CMErrorTrueNorthNotAvailable
} CMError;

It seems error 102 is CMErrorTrueNorthNotAvailable, and its description is

CMErrorTrueNorthNotAvailable

It seems not much information is available regarding what causes this error. It can be any hardware issue with the device.

answered Jan 02 '13 at 11:27

Krishnabhadra

34,169
30
118
167

Thanks, I somehow missed that in the documentation. The docs also state: "This usually indicates that the device’s location is not yet available." Strange, because Core Location seems to work. – Ortwin Gentz Jan 02 '13 at 11:58

score 2 · Answer 3 · answered Jan 10 '18 at 17:03

2

Also, make sure this is enabled. After I enabled this option, I did not encounter the 102 issue anymore while using xTrueNorthZVertical.

Settings > Privacy > Location Services > System Services > Compass Calibration

answered Jan 10 '18 at 17:03

inigo333

3,088
1
36
41

score 0 · Answer 4 · answered Jan 02 '13 at 11:27

0

102 is CMErrorTrueNorthNotAvailable. I guess that your device has problems with determining north direction or something.

answered Jan 02 '13 at 11:27

Mateusz

314
1
5

score 0 · Answer 5 · answered Dec 23 '14 at 07:01

0

I got this error and when i tried to find solution, apparently my location services in my device are switched off, once i switched on, it worked.

answered Dec 23 '14 at 07:01

santhu

4,796
1
21
29

What does Core Motion error 102 mean?

5 Answers5

Linked