The file "[...].entitlements" could not be opened

[smith-chris]

Summary

Hey guys, I have a problem with eas. It wont built & throws this error:
error: The file "/Users/expo/workingdir/build/ios/TestNotificationService/TestNotificationService.entitlements" could not be opened. Verify the value of the CODE_SIGN_ENTITLEMENTS build setting for target "TestNotificationService" is correct and that the file exists on disk. (in target 'TestNotificationService' from project 'FlickAssistant')
and i think its related to this warning which appears when i run eas build -p ios
» ios: paths-entitlements: Found multiple *.entitlements file paths, using "ios/FlickAssistant/FlickAssistant.entitlements". Ignored paths: ["ios/TestNotificationService/TestNotificationService.entitlements"]

Environment

EAS CLI 0.38.0 environment info:
System:
OS: macOS 11.5.2
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.17.0 - /usr/local/bin/node
Yarn: 1.22.4 - ~/.yarn/bin/yarn
npm: 6.14.13 - /usr/local/bin/npm
Utilities:
Git: 2.32.0 - /usr/local/bin/git
npmPackages:
react: 17.0.1 => 17.0.1
react-dom: 16.9.0 => 16.9.0
react-native: 0.64.0 => 0.64.0
npmGlobalPackages:
eas-cli: 0.23.0

Error output

No response

Reproducible demo or steps to reproduce from a blank project

1. create blank react native project
2. in xcode add file->new target->notification service extension
3. in notification service extensions add capability->app groups, create & select an app group
4. run eas build -p ios

[dsokal]

Hi @smith-chris,
Thanks for reporting! Unfortunately, I couldn't repro the issue - the steps you provided are too generic. Could you please share a repo (e.g. on GitHub) with a reproducible demo? Thanks!

[smith-chris]

thank you for looking into in @dsokal . ill try to provide a repo soon

[smith-chris]

but just regarding eas build -p ios » ios: paths-entitlements: Found multiple *.entitlements file paths, using "ios/FlickAssistant/FlickAssistant.entitlements". Ignored paths: ["ios/TestNotificationService/TestNotificationService.entitlements"], do you know what it is about? why is it ignoring an entitlement path?

[smith-chris]

Seems strange to me as the same version of the project that build successfully like 10 days ago, now fails

[dsokal]

I see that you're using eas-cli@0.38.0. Can you try out the latest version (0.38.1)?

[smith-chris]

Im getting the same warning on it about paths-entitlements so I suspect the result will be the same but I'll let you know

[smith-chris]

Solved it simply by changing the name from TestNotificationService.entitlements -> TestNotificationService.entitlement just so, as I assume, EAS isnt removing it. I still think I shouldn't have to do that though so would be awesome if someone familiar with the EAS source would look into it

[tobiasr]

I think I'm up against the same issue. Couldn't build because of this. Ended up testing the suggested solution of renaming (and changing build settings to point to the renamed file). This makes it possible to build, but something still doesn't work because submitting to Apple then leads to an email warning about "ITMS-90078: Missing Push Notification Entitlement".

To me this is a critical issue. It stops us from being able to use EAS build right now with a configuration that worked a couple of weeks ago.

[tobiasr]

Found the solution for me. The error was that the build was expecting (using the names above) TestNotificationService.entitlements but the file on disk was testnotificationservice.entitlements, so fixing the casing of the file solved it. This have worked before (and worked when building from Xcode) so it seems to be an issue that have appeared somewhere in the build pipeline. Leaving this comment here for someone looking for a fix.

[TomHessburg]

I'm having the exact same issue. Testing @tobiasr's proposed solution now, but I'd bet this is a casing issue for sure. 0 issue building a month or two ago, builds totally fine locally, but I've got an entitlements file which is "mobileRelease.entitlements". Will follow up if I see any issues (testing both a preview and release build)

---

EDIT

Following up, lowercasing my entitlements files names seems to have worked. Of course not ideal, but in case anyone else hits this, can verify that making that change worked for me.

[dsokal]

This should be fixed now.
The fix for local builds (eas build --local) will be included in the next release.