Hi guys,I experience a loss of CMDeviceMotion events (using iOS13.1.x, not tested with ealier releases) initiated using startDeviceMotionUpdatesToMotionQueue() once the app enters background and returns to foreground. The deviceMotionUpdateInterval is set to 100ms.devicemotionData no more occurs. A re-initialisation of CMDeviceMotion is required to recover.My App generally supports location updates in background mode, which seems not a sufficient setting.Any hint? Is HealthKit's HKWorkoutSession the only way?

Hi Guys,since at least 2 years and usage of CMAltimeter, the method startBarometerUpdatesToMotionQueue(withHandler handler: @escaping CMAltitudeHandler) does not support modifying the core update interval fixed at 1 Hz (i.e. updates are output every 1 second).This update rate is not sufficient for sport applications. The embedded hardware (MEMS) of well-known suppliers actually supports higher update rates than 1 Hz.Why does Apple limit the update rate to 1 Hz and does not provide a similar update interval configuration interface as for accelerometer?I've posted this as a new feature request 2 years ago without any apple feedback (via Feedback Assistant): Aug 31, 2018 at 4:35 PM – FB5637206 CMAltimeter: fastest update rate is limited to 1Hz (no configuration of update interval) 43939295How can I start a discussion with Apple engineers to check feasability?I'm missing an interface or method parameter like byInterval interval:TimeInterval in below methodCode snippet open func startBarometerUpdatesToMotionQueue(withHandler handler: @escaping CMAltitudeHandler) { ... }Apple CMAltimeter Documentation: developer.apple.com/documentation/coremotion/cmaltimeterMerci