Notifications filtering request - do we need separate approvals for apps belonging in the same account?

Question

Created 2d

Replies 1

Boosts 0

Participants 2

I have two apps - say A and B in my AppStore account, deployed in the AppStore.

App A has obtained the com.apple.developer.usernotifications.filtering entitlement and this is added to my AppStore account by Apple after approval. Note that this is added for the account, and not for the specific app.

Now, my app B also wants this functionality. Followed all the steps as done for app A - adding the already approved entitlement to my app B's identifier, regenerating the profiles, adding the key in the entitlements file, calling the completion handler with empty content like - contentHandler(UNNotificationContent())

Still the notifications show, the filtering is not working.

Do I have to request the entitlement for App B separately?
Even if I do request again, I am not sure if there is going to be any difference in the steps already done. The difference can only be if Apple has a mapping with the app id internally in their system, for the filtering to work?
If I have white-labelled versions of apps A or B, do I have to request again then?
Or does Apple restrict only one app to have this entitlement from one AppStore account?

Please guide on the next steps here.

Boost

Answer 1

Engineer OP

Apple

1d

Whether this entitlement is assigned on a single app or your team account would depend on the entitlement team's evaluation of your use case at the time you have made the request.

This would be determined on a case by case basis, and the information you received at the time you made the request and received the entitlement would have explained your usage limitations.

Best would be to contact the entitlement team and inquire about the state of your entitlement assignments.

White-labelled apps could be different, depending on what you exactly mean by white-labeled. If the apps are being published by your clients directly, they will need tp apply and acquire the entitlement separately.

In any case, this sounds like you would be better off contacting the entitlements team and inquire.

On the technical side, you could be encountering some other issue, like a build problem not configuring the extension correctly, the extension not being launched, or crashing, etc.

Using the Console app and filtering on your bundle id, you might be able to see if there are any errors in launching the extension, and that could also assist in debugging for any problems in the code that could be causing the failure to filter the notification.

0