Critical Alerts not enabled despite updated provisioning profile and entitlements

Question

Created Oct ’20

Replies 1

Boosts 0

Views 1.5k

Participants 1

I have followed all the documented recommendations for enabling critical alerts in my app, but cannot get it working.

I have verified the following:

my team was granted the entitlement
I issued a new provisioning profile embedding the entitlement
I imported the profile in XCode and use it for signing the app.
XCode is confirming the profile is appropriate and that it has the entitlement.
I added the entitlement in my entitlements plist and double checked that it is the file XCode is using to build the app.
In my authorisation request to the UNUserNotificationCenter I now request the additional type .criticalAlert
On App Store connect I can see the uploaded build is containing the entitlement.

Fearing an iOS issue I checked with a well-known app available on the App Store that has critical alerts enabled whether it was working on my test device and it worked as expected.

But it does not work with my app, meaning:

when I perform the authorization request for the first time, I only get the standard authorization pop-up and it is not followed by the special pop-up for critical alerts.
I do not see the critical alert options in the notification settings of the app.
If my server send a push notification with the appropriate payload for a critical alert, it gets distributed as standard push notification.

I also opened a code-level support requets but as it seems to take some time would appreciate if anyone has insights on this.

thank you

Boost

Answer 1

alexdoo OP

Oct ’20

It turns out I had actually not updated the right piece of code to request the additional .criticalAlert type to the UNUserNotificationCenter. (had updated an old piece of code that no longer runs...)

It is worth noting that even with the appropriate entitlement, the Notifications settings for your app won't show the "Critical alert" control until your app has made the authorization request for the .criticalAlert. I need to dig a bit more to understand what this implies to migrate existing users who already have been exposed to the once in the lifetime notification authorization pop-up...

0