Posts

Post not yet marked as solved
7 Replies
2.0k Views
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
Posted Last updated
.
Post not yet marked as solved
0 Replies
317 Views
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?
Posted Last updated
.
Post not yet marked as solved
0 Replies
367 Views
Hi guys,I'm activating CoreMotion and CoreLocation in the following order (but may not be the issue here)startBarometerUpdatesToMotionQueue { (altitudeData, error) in ... // with default 1s data provision interval startAccelerometerUpdatesToMotionQueue { (accellerometerData, error) in ... // with 150 ms data provision interval startUpdatingLocation() // with min. 1s data provision interval startUpdatingHeading() // with same update rate as LocationUnder certain undetermined conditions. e.g. cpu load, the activated services won't provide any data, eventhough the initialisation and activation proceeds error free.Observed:Both CoreMotion and CoreLocation are activated and do not throw any exception or error,CoreMotion and CoreLocation data is not provided.Expected:CoreMotion and CoreLocation data is provided in regular intervals as configured.Reproducibility:Either always or never, meaning on certain devices the issue is intrinsic on other never. It seems like a performance issue.Remediation:Decrease update rate of Accelerometer to 500ms.Remark: when starting the CoreMotion and CoreLocation immediately on App start (e.g. using 3D Touch), the solution to resolve the situation was to delay sensor activation especially to support data feeding of gyrometer.I think the issue here is the kind of concurreny/competition in sensor activation.Is there a way to diagnose the origin of missing data feed?Reference: Feedback Assistant: Oct 24, 2019 at 7:56 PM – FB7406013
Posted Last updated
.
Post not yet marked as solved
1 Replies
1.1k Views
Hi Guys,my app has a UIViewController transition style "Curl" with active animation between 2 UIViewController A (Initial ViewController) and B.The UIViewController transition from A -> B (Segue kind "Show (e.g. Push)") with transition style "Curl" works fine.Leaving UIViewController B by a storyboard segue (UIStoryboardSegue) of Kind "Show Detail e.g. (Replace)" with active animation to UIViewController A does not animate the UIViewController's View to roll back the Curl animation. Instead, the UIViewController A's view remains in a partial curl while the view A and its gesture recognition is still visible/active.Both UIViewConroller A and B are embedded in a UISplitViewController.Observed: The View A remains half-rolled/curled.Expected: The View A rolls back to its default layout/style, when leaving/replacing the View B by View A.Reproducibility: The issue is always reproducible and has been introduced with iOS13.x onwards. All UIViewController View transition worked fine with former iOS verisons (e.g. 12.x).I have posted a bug report via feedback assistant 4 weeks ago (Sep 28, 2019 at 8:12 AM – FB7331595 UISplitViewControlle freezes master view layout during animation), but there's no Apple response yet.I'm therefore turning this issue report to the developer forum.The application does not throw any exception or error.Any hint?
Posted Last updated
.