Hi there! I have multiple end users experiencing the same crash with my last version uploaded to the store. Here is the crash log: 2023-06-07_20-09-20.8360_-0700-a484370f799926bece3fb1b558440c5a30adea8f.crash I was trying to understand the logs and it seems the user is launching the app on Thread 0 frames 22 to 19 and then on frames 12, 11, and 10 some methods from FrontBoardServices framework are being called. After that, C++ library calls a terminate method and on frame 5 I see an objc-exception and right after that, the app is killed by the OS. This crash only happens with end users. Our QA team and development team are not able to replicate it. Is this FrontBoardServices a private framework? I didn't find any information about it. I don't understand in which circumstances this framework is being used. Any information you can give will be very welcome. Thanks

Hi there! I am checking the authorizationStatus() of CMMotionActivityManager when Motion toggle disabled in phone's Settings Privacy Motion & Fitness. I get a correct status of "restricted" for system wide restrictions. When I enable the toggle, and bring my app back to foreground from background, the authorizationStatus() still returns "restricted". If I swipe-out/terminate the application and relaunch, it then changes the authorization status. The same happens when the app is reinstalled. Is there a way to refresh the authorizationStatus() when bringing the app from background to foreground? Thanks!