Post

Replies

Boosts

Views

Activity

FamilySelectionPicker crashes due to internal memory limit
Disclaimer The setup of the FamilyControls capability, authorization etc. is all correct and properly working. The Issue Users complain that apps are not shown up on their parent device. Investigations For months we thought it's a syncing issue and eventually apps do show up. But another time (after already shown) they hide again. Insights We now found out, that the FamilyControlsAgent which is an internal process of iOS crashes due to exceeding their memory limit right before the picker should show up and then logs errors that it can't connect to "helper process". Feedback Tickets: Including multiple sys-diagnose files, step by steps and more: FB11983206 FB11863463 FB11983304 Attention As more and more users get frustrated with it, we hope some Apple engineer sees this and helps bring attention to a fast bug fix. Maybe just increase internal memory limit threshold for such process via entitlement. FYI We also think this is the reason why the DeviceActivityReport can't show apps and crashes due this limitation. But I would much rather prefer Apple to focus on the memory crash. FB11787794
0
2
616
Feb ’23
Must the APNs token for a location-query notification be handled differently than a normal push token?
Hi, I've successfully requested the entitlement for com.apple.developer.location.push with Apple. After creating all relevant provisioning profiles, Push Services Key etc. and verifying that a visible push notification arrives to my physical device I'm stuck when trying to send a location push notification to wake up my Push Location Service extension. I use Firebase FCM to trigger the Push Notification which returns me one of the two things: Success when I try to send a visible notification DeviceTokenNotForTopic (when I try to send a background notification) Invalid Argument - invalid registration token when I try to send a location push notification with the apn headers: apns-push-type --> location apns-topic --> <bundle-id-of-the-main-app>.location-query apns-priority --> 10 (also tried with 5) Is there anything missing to be able to send a location push-type notification? Can I reproduce this without FCM in a easy way via command-line? Thanks!
3
0
1.9k
Jan ’22
FamilySelectionPicker crashes due to internal memory limit
Disclaimer The setup of the FamilyControls capability, authorization etc. is all correct and properly working. The Issue Users complain that apps are not shown up on their parent device. Investigations For months we thought it's a syncing issue and eventually apps do show up. But another time (after already shown) they hide again. Insights We now found out, that the FamilyControlsAgent which is an internal process of iOS crashes due to exceeding their memory limit right before the picker should show up and then logs errors that it can't connect to "helper process". Feedback Tickets: Including multiple sys-diagnose files, step by steps and more: FB11983206 FB11863463 FB11983304 Attention As more and more users get frustrated with it, we hope some Apple engineer sees this and helps bring attention to a fast bug fix. Maybe just increase internal memory limit threshold for such process via entitlement. FYI We also think this is the reason why the DeviceActivityReport can't show apps and crashes due this limitation. But I would much rather prefer Apple to focus on the memory crash. FB11787794
Replies
0
Boosts
2
Views
616
Activity
Feb ’23
Must the APNs token for a location-query notification be handled differently than a normal push token?
Hi, I've successfully requested the entitlement for com.apple.developer.location.push with Apple. After creating all relevant provisioning profiles, Push Services Key etc. and verifying that a visible push notification arrives to my physical device I'm stuck when trying to send a location push notification to wake up my Push Location Service extension. I use Firebase FCM to trigger the Push Notification which returns me one of the two things: Success when I try to send a visible notification DeviceTokenNotForTopic (when I try to send a background notification) Invalid Argument - invalid registration token when I try to send a location push notification with the apn headers: apns-push-type --> location apns-topic --> <bundle-id-of-the-main-app>.location-query apns-priority --> 10 (also tried with 5) Is there anything missing to be able to send a location push-type notification? Can I reproduce this without FCM in a easy way via command-line? Thanks!
Replies
3
Boosts
0
Views
1.9k
Activity
Jan ’22