Entitlements in your app bundle signature do not match the ones that are contained in your provisioning profile

Question

I'm getting a weird issue, I've not changed any expo settings in the expo app.json, and suddenly Apple is rejecting the archive with the following reason:

ERROR ITMS-90164: "Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '[]' for the key 'com.apple.security.application-groups' in 'Payload/ExpoKitApp.app/com.company.appname'.

My expo config is as shown below:

{
  "expo": {
    "name": "App Name",
    "slug": "app-name-slug",
    "version": "1.1.1",
    "orientation": "portrait",
    "icon": "./src/assets/icon.png",
    "splash": {
      "image": "./src/assets/splash.png",
      "resizeMode": "cover",
      "backgroundColor": "#000000"
    },
    "updates": {
      "fallbackToCacheTimeout": 0
    },
    "assetBundlePatterns": [
      "**/*"
    ],
    "ios": {
      "supportsTablet": false,
      "bundleIdentifier": "com.company.appname",
      "buildNumber": "1.1.1",
      "infoPlist": {
        "NSCameraUsageDescription": "App Name uses your camera to allow you to upload a profile picture.",
        "NSPhotoLibraryUsageDescription": "App Name uses your photos to allow you to upload a profile picture."
      }
    },
    "android": {
      "package": "com.company.appname",
      "versionCode": 13,
      "permissions": []
    },
    "web": {
      "favicon": "./src/assets/favicon.png"
    },
    "androidStatusBar": {
      "barStyle": "light-content",
      "backgroundColor": "#042f3d"
    },
    "androidNavigationBar": {
      "barStyle": "dark-content",
      "backgroundColor": "#042f3d"
    },
    "description": ""
  }
}

Admittedly this is the first issue I've had with the Apple Review system (this is the first app) so I have no idea where to look. Any help would be appreciated.

Edit: I use expo on windows, and I have App Store Connect.

This is not an answer. However just today I have started receiving the same flavor of error (entitlements issue, noting an empty array for an entitlement value) on a react-native app I'm attempting to submit to the store. Submission worked yesterday, developer profile and entitlements file are both unchanged from successful submission. Perhaps something changed upstream on the apple dev site and profiles need re-syncing, that is my next investigative step. Good luck — Mike Hardy, Jan 14 '21 at 15:03
@jspizziri I just posted a real answer below, after achieving successful app submission — Mike Hardy, Jan 14 '21 at 16:15
Does this answer your question? [The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile](https://stackoverflow.com/questions/65712249/the-entitlements-in-your-app-bundle-signature-do-not-match-the-ones-that-are-con) — Peter O., Jan 15 '21 at 09:53

Mike Hardy · Answer 1 · 2021-01-14T16:41:25.590

I am open to correction on this answer of course, but as mentioned in a comment above:

Guess at root cause: (Apple App Store is a closed system, we may only guess)

I believe the Apple back-end has changed as of today, and has started applying a stricter rule to entitlement keys that take array values.

I believe the Apple back-end used to accept empty arrays for entitlement keys that took array values but now requires the entitlement key to either not be present at all, or to contain actual values.

Evidence to back this assertion:

I have an entitlements file with a key for "in-app-messaging" entitlement with an empty array like so:

        <key>com.apple.developer.in-app-payments</key>
        <array/>

This was fine until just yesterday (I successfully submitted a build, and have submitted builds like this for more than a year.
Now it is no longer fine, and you have a similar empty array message in your error.

The fix:

Open the .xcworkspace (Xcode project) file and navigate to the signing and entitlements for my project, and remove the offending entitlement key

The key was empty anyway so should not have an effect other than now the entitlements file has exactly the lines I quoted above removed

The App Store submission is successful.

That's good, it sounds like my issue. Since I'm on windows and using expo to build, I don't have an .xcworkspace though, and the expo docs don't mention how to change these: https://docs.expo.io/versions/latest/config/app/ — Ashley Williams, Jan 14 '21 at 17:03
There is nothing to do but file an upstream issue then unfortunately. Fortunately in my experience maintaining react-native repositories and interacting with the expo folks they are *very* responsive. — Mike Hardy, Jan 14 '21 at 17:22

score 0 · Accepted Answer · answered Jan 15 '21 at 16:37

To fix this issue (even if you are using the Expo managed workflow and don't have access to the .entitlements file) go into your Apple Developer portal's "Identifiers" tab, open up the relevant app ID, and make sure that you don't have any items checked but not configured.

For example, in this case it looks like you have the app groups item checked, but no app groups actually configured, so it looks like this:

Entitlements in your app bundle signature do not match the ones that are contained in your provisioning profile

2 Answers2