EAS build iOS Build failed Production

[Janendran]

Build/Submit details page URL

No response

Summary

[RUN_FASTLANE] ▸ ARCHIVE FAILED [RUN_FASTLANE] 2023-08-25 23:48:47.716 xcodebuild[8390:76551] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled) [RUN_FASTLANE] ARCHIVE FAILED [RUN_FASTLANE] Exit status: 65

Managed or bare?

managed

Environment

eas build --platform ios

Error output

[RUN_FASTLANE] ▸ ARCHIVE FAILED [RUN_FASTLANE] 2023-08-25 23:48:47.716 xcodebuild[8390:76551] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled) [RUN_FASTLANE] ARCHIVE FAILED [RUN_FASTLANE] Exit status: 65

Reproducible demo or steps to reproduce from a blank project

eas build --platform ios

[1eokim]

I'm going through the exact same issue while attempting internal distribution build for iOS.

[szdziedzic]

Hi, I believe you should look into Xcode logs for more useful information regarding this issue. Are you using the--local mode of EAS CLI?

[1eokim]

Hi, I believe you should look into Xcode logs for more useful information regarding this issue. Are you using the--local mode of EAS CLI?

Hi, I'm fairly new to EAS CLI, and I'm not exactly sure how to find out which mode I'm using. Could you walk me through the process? Also, any thoughts on how to circumvent this issue when attempting internal distribution build for iOS? I'm following the tutorial on Expo website, but the error persists.

[szdziedzic]

You are using the eas build --platform ios command, right? Can you send me the link to your build?

[tristian-azuara-sh]

We're having the same issue. The build fails when ran using eas build but succeeds when archived using Xcode directly.

[Tagir-A]

Same here. Simulator local build are fine, but device targeted local builds fail for development, preview and production. Build on Expo infra are fine, the problem is only with local builds.

The problem disappeared when I rolled back to eas-cli@5.0.0

[szdziedzic]

We only did small unrelated bug fixes between 5.0.0 and 5.0.2. It seems like we didn't change anything related to local builds.

The Run Fastlane build phase contains only very generic logs. I believe that you probably can find more information in Xcode logs. They are visible as a separate phase on your build details phase when you are using EAS Build on Expo infra. You can use variables explained in https://docs.expo.dev/build-reference/local-builds/#using-local-builds-for-debugging to get to the Xcode logs for local builds and debug them.

[Pcummings]

I am seeing this issue too using both eas-cli versions 5.0.0 and 5.2.0. Here's a link to my build https://expo.dev/accounts/fairtasting/projects/fairTasting/builds/82f6ee4d-8dfb-4043-b456-4dca675d7e7c

[gunslingerOP]

SOLUTION : I was facing this issue and after nuking all my certificates from the apple portal then even provisioning a new profile alongside the new credentials, I managed to fix this error. It has nothing to do with the expo cli version. Please close this issue.

[ndpiparava]

@gunslingerOP Please do not generalise your experience, I did same and does not work for me.

[ChristopherGabba]

I'm also facing this issue with building a expo dev client and its failing on fastlane with the same error.

[jjspierx]

I am also facing this issue after upgrading to Expo SDK 49 in a managed workflow. Happens using EAS build for dev clients as well as for Production clients. I've tried deleting all my certs and provisioning profiles and recreating, but that did not fix the issue for me.

[alpereryurt]

Updating eas-cli to the latest version (eas-cli/5.4.0) solved my problem.

npm install -g eas-cli

[james-likeclockwork]

We are also having this issue, or at least there is some overlap in our issues:

Fastlane Logs:

set -o pipefail && xcodebuild -workspace ./boxicompanion.xcworkspace -scheme boxicompanion -configuration Release -destination 'generic/platform=iOS' -archivePath /Users/expo/Library/Developer/Xcode/Archives/2023-10-08/boxicompanion\ 2023-10-08\ 09.52.51.xcarchive archive | tee /Users/expo/workingdir/logs/boxicompanion-boxicompanion.log > /dev/null

▸ 2023-10-08 09:52:51.992 xcodebuild[4691:13926] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)

Run script build phase '[CP-User] Generate app.config for prebuilt Constants.manifest' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXConstants' from project 'Pods')

Run script build phase 'Start Packager' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'boxicompanion' from project 'boxicompanion')

Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'boxicompanion' from project 'boxicompanion')

▸ ARCHIVE FAILED

XCode Logs:

2023-10-08 09:52:51.992 xcodebuild[4691:13926] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)

ARCHIVE FAILED

Exit status: 65

warning: Run script build phase '[CP-User] Generate app.config for prebuilt Constants.manifest' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXConstants' from project 'Pods')

/Users/expo/workingdir/build/ios/boxicompanion.xcodeproj: error: Provisioning profile "ad_ho_world_prov" doesn't support the Push Notifications capability. (in target 'boxicompanion' from project 'boxicompanion')

/Users/expo/workingdir/build/ios/boxicompanion.xcodeproj: error: Provisioning profile "ad_ho_world_prov" doesn't include the aps-environment entitlement. Profile qualification is using entitlement definitions that may be out of date. Connect to network to update. (in target 'boxicompanion' from project 'boxicompanion')

warning: Run script build phase 'Start Packager' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'boxicompanion' from project 'boxicompanion')

note: Run script build phase '[Expo] Configure project' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'boxicompanion' from project 'boxicompanion')

warning: Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'boxicompanion' from project 'boxicompanion')

[MaxVickii]

Also facing this exact same issue but only when our project contains certain dependencies (customerio-reactnative and matching expo plugin), after removing those two the iOS production build went through again.

Any idea of how to fix this?

[james-likeclockwork]

@MaxVickii My issue seemed to be related to enabling Rush Notification permissions for the application on the app store side of things. Then creating a new certificate and provisioning profile.

I got to this conclusion by doing a local build which provided better error messaging.

Hope you get resolved quickly.

[a-eid]

I believe this might be the actual error message

 xcodebuild[39222:30929508] Requested but did not find extension point with identifier Xcode.InterfaceBuilderBuildSupport.PlatformDefinition

which I'm not sure how to resolve yet, it's related to one of the packages I installed recently on an added entitlement.

[sevketaydogdu]

SOLUTION : I was facing this issue and after nuking all my certificates from the apple portal then even provisioning a new profile alongside the new credentials, I managed to fix this error. It has nothing to do with the expo cli version. Please close this issue. @gunslingerOP this is worked for me, thank you so much

[nfuenmamelt]

SOLUTION : I was facing this issue and after nuking all my certificates from the apple portal then even provisioning a new profile alongside the new credentials, I managed to fix this error. It has nothing to do with the expo cli version. Please close this issue. @gunslingerOP this is worked for me, thank you so much

Can you tell me what you mean by nuking all certificates and profiles?

[nfuenmamelt]

SOLUTION : I was facing this issue and after nuking all my certificates from the apple portal then even provisioning a new profile alongside the new credentials, I managed to fix this error. It has nothing to do with the expo cli version. Please close this issue. @gunslingerOP this is worked for me, thank you so much

Can you tell me what you mean by nuking all certificates and profiles?

Done forget this.

[Anyamborogass]

SOLUTION : I was facing this issue and after nuking all my certificates from the apple portal then even provisioning a new profile alongside the new credentials, I managed to fix this error. It has nothing to do with the expo cli version. Please close this issue.

This worked for me. Turns out my profiles under "Certificates, Identifiers & Profiles" were invalid... Deleted every cert (except the merchant one) and profile and the build worked!

[domodu-apps]

after nearly depleting my free iOS EAS build credits for the month, I solved it by:

• placing the 'onesignal-expo-plugin' first on the list
• most important I think, deleting and creating new Build Credentials and a Push Notifications key. Not on the Apple website(which you could still do I guess), just by using 'eas credentials' with the eas cli.

[rijulaggarwal16]

After so many tries, deleting and creating new build credentials on apple developer website solvved it for me. To be precise, I deleted it myself and let eas generate a new one when I ran eas build.

[vishaljnimblechapps]

@rijulaggarwal16 I have exactly do the same but still i'm facing a same issue. Anyone have the solution ? Please let me know.

[tmw102]

I was able to resolve this by running eas credentials through the cli and selecting 'Set up all the required credentials to build your project'. As others have mentioned this is probably more straightforward than altering the Apple certificates directly on the Apple Developer website.

[eriktoor]

Hey folks I had this same issue and all I needed to do to fix this is to upgrade my eas cli. After doing this the issue was fixed.

I ran $ npm install -g eas-cli

[berataras]

Even after updating eas-cli, I found that it remained on the old version when I ran the eas -v command. Later, I realized that I had installed the eas-cli package not with npm but with Homebrew. Then, when I executed the following commands, eas was successfully updated:

brew uninstall eas-cli (if this doesn't work, continue below)

npm uninstall -g eas-cli

which eas

sudo rm /opt/homebrew/bin/eas (replace with your actual path)

npm install -g eas-cli

This cleanly removes eas-cli and allows you to reinstall it with the latest version.

and my eas.json:

  "cli": {
    "version": ">= 5.1.0"
  },

When I completed all of these steps, the build was successful.