Missing Push Notification Entitlement Warning

Missing Push Notification Entitlement issues

open your project target and then go to Signing & Capabilities then click in the + Capability and select Push Notification it should appear to you like the image

Missing Push Notification Entitlement

Yes, that's the cause of the App Store rejection. If your ad-hoc provisioning profile has the aps-environment key, it means your app is configured correctly in the Apple Provisioning Portal. All you need to do is delete the App Store distribution profile on your local machine, then re-download and install the distribution profile from the Provisioning Portal. This new one should contain the aps-environment key.

Flutter iOS app submission issue warning: Missing Push Notification Entitlement

Word on the street is that as long as you really don't use push notifications this will not cause your app to get rejected. So you can safely (?) ignore this warning and continue to submit your app.

This issue was described on GitHub here, and a solution is being discussed here. It's apparently somehow related to Flutter using the UIApplicationDelegate callback:

- (void)application:(UIApplication*)application
    didReceiveRemoteNotification:(NSDictionary*)userInfo
          fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler;

I'll let someone else explain the exact reason more clearly. Keep an eye on the GitHub issue.

For now I am just going to ignore the warning.

Update: I submitted my app, it was accepted, and there hasn't been any problem with it since then. So just ignore the warning.

React Native, ITMS-90078: Missing Push Notification Entitlement

Add the push notification capability in signing&capability -> capability -> push notification. Make sure to add It to both the release and debug tab.

iOS - Missing Push Notification Entitlement

Get a developer build

Get your developer to give you the .IPA file that is signed using their normal “iPhone Developer” key. They do this all the time to test the app on physical devices they own

Get your tools in order

You will need the following:

1. A “Mobile Provisioning Profile”
2. An “Entitlements.plist”
3. An “iOS Distribution Certificate”
4. iReSign OS X app (or you could use command line)

1. Mobile Provisioning Profile

Download (or create then download) this from the “iOS Provisioning Profiles”inside of Apple Developer Members Center.

2. Entitlements Plist

You will actually need to make this yourself. You will need two values to make the strings required. You need the App ID Prefix and the Bundle ID. You can find them in Members Center “Certificates, Identifiers & Profiles”

Open your favorite text/code editor and drop this in. Then update the two values in the following code and save it as “entitlements.plist”.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>aps-environment</key>
    <string>development</string>
    <key>get-task-allow</key>
    <false/>
</dict>
</plist>

If you are NOT using Push Notifications, you need to remove the two lines:

<key>aps-environment</key>
    <string>production</string>

3. iOS Distribution Certificate

You should have this installed already. If not, you can get it installed via Xcode or Member Center.

1. Xcode > Preferences > Accounts
2. Find or add your Apple ID and click “View Details”
3. ”+” “iOS Distribution” (or iOS Development) and then Refresh (bottom left)

Missing Push Notification Entitlement?

The solution is to do what it says:

If your app does not use the Apple Push Notification service, no
action is required.

It seems fairly clear by unless I'm missing something.

Missing Push Notification Entitlement, even with aps-environment entitlement set. iOS and Testflight

After a multi - hour debug session with a friend of mine that is better versed in Apple processes than I am, we managed to figure out the issue. Everything was set up correctly... all my certs were in line, all of the profiles and Bundle IDs matched, everything looked good. The issue was for some reason, xcode was displaying all of my certs from appstoreconnect and developer.apple.com, but it was not including a local entitlements file with the binary that ultimately got uploaded to app store connect, which drew the error, and ultimately prevented push notifications from working. The fix was simple... just click "+ capability" next to "all" in signing and capabilities, search for and add push notifications, and bingo! This adds the proper entitlements to my binary, which then look for the certs in app store connect. This now uploads without the error message and push notifications on any installs from this new build starting working immediately. I hope this helps someone, someday! Apple, please make this more straightforward, or don't let xcode lie about its certs!

Missing Push Notification Entitlement

I am pretty certain that it is a bug in Apples checking system. I uploaded an app yesterday and got this message. This app has been updated at least 30 times without any problems. I didn't add any push notification code in the last version and I don't use any frameworks like PhoneGap or Cordova that could cause this message. It doesn't appear under notifications on the device.

I have searched the app for push notification code without finding anything:

grep -r "registerUserNotificationSettings" .

grep -r "registerForRemoteNotificationTypes" .

I finally tried to upload the previous version that was approved in July (and didn't generate an email). This this time I got the warning email also for this version. So I think that Apple is wrong and I will take my chances and hope it will be approved despite the warning.

---

EDIT: Found this reply from an Apple staff in Apple Developer Forum:

"That notice is a warning only, not a rejection.

The app validator checks for an implementation of the UIApplicationDelegate method application:didRegisterForRemoteNotificationsWithDeviceToken: in the app. You’ll get the warning you described if your app delegate implements that method and there is no aps-environment entitlement.

It's possible that a third-party library you're using has implemented that method even though your app doesn't do anything with push notifications. In that case you can just ignore the warning. It's there to let developers who do use push notifications know if they might have signed their app incorrectly."

---

EDIT 2: I now have two different apps that have been approved without any problems despite generating the warning email

---

Related Topics