CMMotionManager sometimes provides motion updates AFTER stopDeviceMotionUpdates is called

Originator:jerry
Number:rdar://15872980 Date Originated:Jan 21 2014
Status:Open Resolved:
Product: Product Version:
Classification: Reproducible:
 
Summary:
If using the startDeviceMotionUpdatesToQueue:withHandler: method on CMMotionManager, it is sometimes possible the motion updates will be provided after stopDeviceMotionUpdates is called.

Steps to Reproduce:
1. Create a motion manager
2. call startDeviceMotionUpdatesToQueue:withHandler:
4. call stopDeviceMotionUpdates
5. watch for the block provided in startDeviceMotionUpdatesToQueue:withHandler: to be executed

Expected Results:
The motion manager should not provided updates after stopDeviceMotionUpdates has been called.

Actual Results:
In some instances, the block provided in startionMotionUpdatesToQueue:withHandler is called after stopDeviceMotionUpdates is called.

Version:
iOS SDK 7.0

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!