[stderr] [11:09:40] [ios.entitlements]: withIosEntitlementsBaseMod: Entitlements plist is empty

[GautierT]

Hi.
On EAS from Expo when I run eas build --profile staging --platform ios
On the Prebuild step I have this error :

Prebuilding managed project
- Clearing ios
✔ Cleared ios code
- Creating native project directories (./ios and ./android) and updating .gitignore
✔ Created native project | gitignore already synced
- Adding Metro bundler config
✔ Added Metro config
- Updating your package.json scripts, dependencies, and main file
✔ Updated package.json and added index.js entry point for iOS and Android
- Config syncing
✖ Config sync failed
[stderr] [11:09:40] [ios.entitlements]: withIosEntitlementsBaseMod: Entitlements plist is empty
bash exited with non-zero code: 1

My plugins array from app.config.js is

"plugins": [
    "sentry-expo",
    "@react-native-mapbox-gl/maps",
    "@config-plugins/android-jsc-intl",
    [
      "@config-plugins/react-native-branch",
      {
        "apiKey": "BRANCH_API_KEY",
        "iosAppDomain": "test.app.link"
      }
    ],
    [
      "onesignal-expo-plugin",
      {
        "mode": "production"
      }
    ]
  ],

If i remove the onesignal-expo-plugin part the build is successful

Their is a provisioning profile configured by eas on my apple account like this :

And the app id configuration is associated to a production certificate.

I don't what I'm doing wrong on the config side.

Thanks.

[GautierT]

I tried locally and the problem is the same :

If i remove

    [
      "onesignal-expo-plugin",
      {
        "mode": "production"
      }
    ]

The prebuild is okay.
Example locally :

❯ expo prebuild --platform ios --clean
Warning! Your git working tree is dirty.
It's recommended to commit all your changes before proceeding, so you can revert the changes made by this command if necessary.

✔ Would you like to proceed? … yes

✔ Cleared ios code
✔ Created native project | gitignore already synced
✔ Updated package.json and added index.js entry point for iOS and Android
🧶 Using Yarn to install packages. Pass --npm to use npm instead.
✔ Installed JavaScript dependencies 663ms
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
✔ Config synced
✔ Installed pods and initialized Xcode workspace.

But with

❯ expo prebuild --platform ios --clean

Warning! Your git working tree is dirty.
It's recommended to commit all your changes before proceeding, so you can revert the changes made by this command if necessary.

✔ Would you like to proceed? … yes

✔ Cleared ios code

✔ Created native project | gitignore already synced
✔ Updated package.json and added index.js entry point for iOS and Android
🧶 Using Yarn to install packages. Pass --npm to use npm instead.
✔ Installed JavaScript dependencies 652ms
✖ Config sync failed
[ios.entitlements]: withIosEntitlementsBaseMod: Entitlements plist is empty

And indeed, ios/PROJECT/project.entitlements is empty

[jkasten2]

@GautierT Thanks for reporting. Could you provide steps on reproducing the issue from a new project or share an existing project with the error?

[GautierT]

Hi @jkasten2
It seems to be a compatibility problem with @config-plugins/react-native-branch
When I change the order of the plugins array and I put @config-plugins/react-native-branch last the entitlements are correctly set.

Don't Work ❌

"plugins": [
    "sentry-expo",
    "@react-native-mapbox-gl/maps",
    "@config-plugins/android-jsc-intl",
    [
      "@config-plugins/react-native-branch",
      {
        "apiKey": "BRANCH_API_KEY",
        "iosAppDomain": "test.app.link"
      }
    ],
    [
      "onesignal-expo-plugin",
      {
        "mode": "production"
      }
    ]
  ],

Work ✅

"plugins": [
    "sentry-expo",
    "@react-native-mapbox-gl/maps",
    "@config-plugins/android-jsc-intl",
    [
      "onesignal-expo-plugin",
      {
        "mode": "production"
      }
    ],
    [
      "@config-plugins/react-native-branch",
      {
        "apiKey": "BRANCH_API_KEY",
        "iosAppDomain": "test.app.link"
      }
    ]
  ],

Now I'm still fighting with the provisioning profile here with the others ! #40

Thanks !

[rgomezp]

Howdy,
Thanks for reporting @GautierT .

We just released a new beta version that patches some issues related to the entitlements. I wonder if updating will resolve this issue for you. Please give it a shot and update here.

In terms of the provisioning profile problems, are you seeing this issue exclusively in the cloud build environment (EAS)? We are investigating that issue but unfortunately, the fastlane error doesn't provide much info regarding the failure. We're working with Expo directly to try to get it resolved. Leave your response / any extra details in the corresponding ticket.

Cheers

[rgomezp]

Closing due to inactivity