Fix: Missing Push Notification Entitlement in App Store Connect

Fix: Missing Push Notification Entitlement in App Store Connect
Quick answer: The Missing Push Notification Entitlement warning or rejection happens when your app registers for remote notifications, but the App Store Distribution provisioning profile used to sign the build lacks the aps-environment entitlement. Delete the cached distribution profile from your Mac, ensure Push Notifications are enabled on your App ID in the Apple Developer portal, and regenerate or re-download the profile before archiving again.

Why this happens

When you upload a build to App Store Connect, Apple scans the compiled binary for calls to remote notification APIs such as UIApplication.shared.registerForRemoteNotifications(). If your app—or any third-party SDK bundled in your app—contains this registration call, Apple expects the app’s code signature to include the aps-environment entitlement.

If that entitlement is missing from the signed archive, App Store Connect rejects the upload or sends a Missing Push Notification Entitlement notice. A common reason this catches developers off guard is that an Ad Hoc provisioning profile may already contain aps-environment, while the App Store Distribution profile on the same Mac does not.

This mismatch usually occurs when Push Notifications were enabled on the App ID after the App Store Distribution provisioning profile was originally created or downloaded. Xcode continues signing with the stale cached profile on disk, or the target’s .entitlements file and Signing & Capabilities configuration are out of sync with the portal.

How to fix it

1. Delete stale provisioning profiles and re-download

If your Ad Hoc profile already includes aps-environment, your App ID is configured properly on Apple’s servers, and your local App Store Distribution profile is simply out of date.

  1. Quit Xcode completely.
  2. Open Finder, press Command + Shift + G, and check both provisioning profile folders for cached .mobileprovision files:
    – ~/Library/MobileDevice/Provisioning Profiles/
    – ~/Library/Developer/Xcode/UserData/Provisioning Profiles/
  3. Delete the existing App Store Distribution provisioning profiles for your app (or clear the folder so Xcode fetches fresh copies).
  4. Open the Apple Developer portal and go to Certificates, Identifiers & Profiles > Profiles.
  5. Locate your App Store Distribution profile. If its status is invalid or it was created before you enabled Push Notifications, click Edit and Save to regenerate it, then download the new .mobileprovision file.
  6. Double-click the downloaded profile to install it, or open Xcode > Settings > Accounts, select your team, and click Download Manual Profiles.

If you use Automatically manage signing in Xcode, deleting the cached profiles and reopening the project forces Xcode to pull a fresh provisioning profile with the updated entitlements.

2. Enable Push Notifications on your App ID and Xcode target

If regenerating the profile does not add aps-environment, verify that Push Notifications are enabled in both the Apple Developer portal and your Xcode project.

  1. In the Apple Developer portal, open Certificates, Identifiers & Profiles > Identifiers and select your app’s Bundle ID.
  2. Scroll to Capabilities, make sure Push Notifications is checked, and click Save.
  3. If you send pushes using certificate-based authentication rather than an APNs Auth Key (.p8), confirm that your Apple Push Notification service SSL certificate is active under the Production section.
  4. In Xcode, select your app target, open the Signing & Capabilities tab, and click + Capability if Push Notifications is not listed.
  5. Check your target’s .entitlements file in the Project Navigator to confirm the APS Environment (aps-environment) key is present:
<?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>
</dict>
</plist>

Xcode sets development in the local .entitlements file and automatically swaps it to production when signing an App Store or Ad Hoc archive.

3. Verify the entitlements before uploading

Before submitting a new build to App Store Connect, confirm that the archived binary actually carries the aps-environment entitlement.

  1. In Xcode, choose Product > Archive.
  2. In the Organizer window, select your new archive and click Distribute App.
  3. Proceed through the App Store Connect distribution flow until you reach the summary screen before uploading.
  4. Expand the entitlements section in the summary and verify that aps-environment is listed with the value production.

You can also inspect an exported .ipa or .xcarchive from Terminal using codesign:

codesign -d --entitlements :- /path/to/YourApp.app

Look for <key>aps-environment</key> followed by <string>production</string> in the output. If it appears there, App Store Connect will accept the signature.

4. Remove unused push registration if your app does not use notifications

Sometimes this error appears in apps that never intend to send push notifications. Analytics, crash-reporting, or marketing SDKs often include registerForRemoteNotifications() internally.

If you do not use push notifications at all, check your dependencies for push-related modules that can be disabled or removed. Otherwise, enabling the Push Notifications capability on your App ID and regenerating your provisioning profile is the fastest way to satisfy Apple’s check without modifying third-party code.

How to prevent it

  • Enable capabilities before creating profiles: Turn on Push Notifications on your App ID in the Apple Developer portal before generating manual Distribution provisioning profiles.
  • Prefer Xcode automatic signing for standard workflows: Automatic signing reduces the chance of archiving with a stale manual profile.
  • Use an APNs Auth Key (.p8) when possible: Unlike per-app SSL certificates, a team-level .p8 key does not expire annually and simplifies server setup.
  • Check the Organizer summary screen: Make it a habit to verify aps-environment: production in the distribution summary before clicking Upload.

FAQ

Why does my Ad Hoc profile have aps-environment while my Distribution profile does not?

Your Ad Hoc profile was likely created or regenerated after Push Notifications were enabled on your App ID, whereas your App Store Distribution profile was cached locally before that change. Regenerating and re-downloading the Distribution profile updates its entitlements to match the App ID.

Should aps-environment in my .entitlements file be set to production?

No, leave it as development in your Xcode project’s .entitlements file. Xcode automatically overrides the value to production when you archive and sign with an Ad Hoc or App Store Distribution provisioning profile.

Can I ignore the Missing Push Notification Entitlement message if my app does not send pushes?

If your app receives this as a warning rather than a hard rejection, the build may still process, but push notifications will not work. However, if App Store Connect rejects the binary, you must either remove the registerForRemoteNotifications() call from your code or dependencies, or enable the Push Notifications capability and re-sign with an updated profile.

Sources & credits

Parts of this guide are adapted from content licensed under CC BY-SA 3.0; this article is shared under the same license.