Hi everyone!
I’ve been using EAS build since April am just now running into this issue. My last build and submit to the app store was ~4 months ago. I just upgraded to the latest version of eas-cli and Im trying to get a new preview build working (“eas build --profile preview --platform ios”). While of course there are changes to the app, nothing has changed between now and my last successful build inside of the ios/ folder.
The actual error that I’m receiving is this:
❌ error: The file "/Users/expo/workingdir/build/ios/MobileApp/mobileRelease.entitlements" could not be opened. Verify the value of the CODE_SIGN_ENTITLEMENTS build setting for target "MobileApp" is correct and that the file exists on disk. (in target 'MobileApp' from project 'MobileApp')
This is strange. I have both a mobile.entitlements file and a mobileRelease.entitlements file in what I believe to be this exact location. I’ve also had these files in the same spot, unmoved, for tens of successful builds in the past (though with an older version of EAS build) I’ve attatched some images below which I think show this.
Anyone have any clues as to what might be going on here?
Thanks!
File structure
XCode “Code Signing Entitlements” paths
Full error message
EDIT:
One other piece of information potentially worth noting:
When updating my eas-cli, I noticed that I also had to completely change my eas.json file (looks like the standard for creating an eas.json file has changed per Configuring EAS Build with eas.json - Expo Documentation).
My old version was the following:
{
"builds": {
"android": {
"release": {
"workflow": "generic"
},
"preview": {
"distribution": "internal",
"workflow": "generic"
}
},
"ios": {
"release": {
"workflow": "generic"
},
"preview": {
"distribution": "internal",
"workflow": "generic"
}
}
}
}
and my new version is:
{
"build": {
"release": {},
"preview": {
"distribution": "internal"
}
},
"cli": {
"version": ">= 0.38.3"
}
}