Fastlane Build Fails on Production in Expo 51 SDK, Fine in Development

[NOxDriver]

Build/Submit details page URL

No response

Summary

I upgraded from SDK 49 to SDK 51 and I have been struggling to build on iOS production.
I use a dev client, and that builds fine on iOS and Android. Android builds fine in production, but just iOS doesn't.

Been trying to find solutions everywhere.
I've reset all my credentials. Removed examples of duplicate object keys etc... But, nothing is working.

I keep on getting this error:

Run script build phase '[CP-User] Generate updates resources for expo-updates' will be run during every build because it does not specify any outputs. To address this issue, 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 'EXUpdates' from project 'Pods')

    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 issue, 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 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this issue, 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 'BoringSSL-GRPC' from project 'Pods')

▸ ** ARCHIVE FAILED **

▸ The following build commands failed:

▸ 	Ld /Users/expo/Library/Developer/Xcode/DerivedData/Appname-Number/Build/Intermediates.noindex/ArchiveIntermediates/Appname/InstallationBuildProductsLocation/Applications/Appname.app/Appname normal (in target 'Appname' from project 'Appname')

▸ 	Archiving workspace Appname with scheme Appname

▸ (2 failures)

** ARCHIVE FAILED **
The following build commands failed:

	Ld /Users/expo/Library/Developer/Xcode/DerivedData/Appname-Number/Build/Intermediates.noindex/ArchiveIntermediates/Appname/InstallationBuildProductsLocation/Applications/Appname.app/Appname normal (in target 'Appname' from project 'Appname')

	Archiving workspace Appname with scheme Appname

(2 failures)

Exit status: 65

​

+---------------------------------------+

|           Build environment           |

+-------------+-------------------------+

| xcode_path  | /Applications/Xcode.app |

| gym_version | 2.225.0                 |

| sdk         | iPhoneOS18.1.sdk        |

+-------------+-------------------------+

Looks like fastlane ran into a build/archive error with your project.
It's hard to tell what's causing the error, so we wrote some guides on how to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/

Before submitting an issue on GitHub, please follow the guide above and make sure your project is set up correctly.

fastlane uses `xcodebuild` commands to generate your binary, you can see the the full commands printed out in yellow in the above log.

Make sure to inspect the output above, as usually you'll find more error information there

[!] Error building the application - see the log above

Error: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.
​

Please can anyone give any suggestions?

Managed or bare?

Managed

Environment

expo-env-info 1.0.5 environment info:
System:
OS: macOS 14.5
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.16.1 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 9.5.1 - /usr/local/bin/npm
SDKs:
iOS SDK:
Platforms: DriverKit 24.1, iOS 18.1, macOS 15.1, tvOS 18.1, visionOS 2.1, watchOS 11.1
IDEs:
Android Studio: 2024.2 AI-242.23339.11.2421.12550806
Xcode: 16.1/16B40 - /usr/bin/xcodebuild
npmPackages:
@expo/metro-config: ^0.18.11 => 0.18.11
expo: ~51.0.39 => 51.0.39
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.74.5 => 0.74.5
npmGlobalPackages:
eas-cli: 13.2.3
expo-cli: 6.3.10
Expo Workflow: bare

✔ Check package.json for common issues
✔ Validate global prerequisites versions
✔ Validate Expo Config
✔ Check compatible dependency versions for the installed Expo SDK
✔ Check for conflicting global packages in project
✔ Check for incompatible packages
✔ Verify prebuild support package versions are compatible

Didn't find any issues with the project!

Error output

No response

Reproducible demo or steps to reproduce from a blank project

run eas build --platform ios
From my expo project with expo ~51.0.39

{
  "name": "appname",
  "version": "1.0.0",
  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "lint": "eslint .",
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web",
    "eject": "expo eject",
    "postinstall": "patch-package"
  },
  "dependencies": {
    "@expo/config-plugins": "~8.0.0",
    "@expo/metro-config": "^0.18.11",
    "@gorhom/bottom-sheet": "^5.0.5",
    "@likashefqet/react-native-image-zoom": "^2.2.0",
    "@react-native-async-storage/async-storage": "1.23.1",
    "@react-native-community/datetimepicker": "8.0.1",
    "@react-native-firebase/analytics": "^21.4.0",
    "@react-native-firebase/app": "^21.4.0",
    "@react-native-firebase/auth": "^21.4.0",
    "@react-native-firebase/firestore": "^21.4.0",
    "@react-native-firebase/functions": "^21.4.0",
    "@react-native-firebase/storage": "^21.4.0",
    "@react-navigation/material-bottom-tabs": "^6.2.29",
    "@react-navigation/native": "^6.1.18",
    "@react-navigation/native-stack": "^6.11.0",
    "@rneui/base": "^4.0.0-rc.7",
    "@rneui/themed": "^4.0.0-rc.7",
    "@sentry/react-native": "~5.24.3",
    "@turf/turf": "^6.5.0",
    "eslint-config-expo": "~7.1.2",
    "expo": "~51.0.39",
    "expo-application": "~5.9.1",
    "expo-av": "~14.0.7",
    "expo-build-properties": "~0.12.5",
    "expo-camera": "~15.0.16",
    "expo-checkbox": "~3.0.0",
    "expo-constants": "~16.0.2",
    "expo-crypto": "^13.0.2",
    "expo-dev-client": "~4.0.29",
    "expo-device": "~6.0.2",
    "expo-file-system": "~17.0.1",
    "expo-haptics": "~13.0.1",
    "expo-image": "^1.13.0",
    "expo-image-manipulator": "~12.0.5",
    "expo-image-picker": "~15.0.7",
    "expo-linking": "~6.3.1",
    "expo-location": "~17.0.1",
    "expo-mail-composer": "~13.0.1",
    "expo-media-library": "~16.0.5",
    "expo-network": "~6.0.1",
    "expo-notifications": "~0.28.19",
    "expo-splash-screen": "~0.27.7",
    "expo-store-review": "~7.0.2",
    "expo-task-manager": "~11.8.2",
    "expo-tracking-transparency": "~4.0.2",
    "expo-updates": "^0.25.27",
    "moment": "^2.29.4",
    "patch-package": "^6.5.0",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-medium-image-zoom": "^5.1.8",
    "react-native": "0.74.5",
    "react-native-confetti-cannon": "^1.5.2",
    "react-native-device-info": "^10.8.0",
    "react-native-dropdown-picker": "^5.4.6",
    "react-native-gesture-handler": "~2.16.1",
    "react-native-google-mobile-ads": "^14.3.0",
    "react-native-iap": "^12.11.0",
    "react-native-image-modal": "^3.0.12",
    "react-native-image-viewing": "^0.2.2",
    "react-native-keyboard-aware-scroll-view": "^0.9.5",
    "react-native-maps": "1.14.0",
    "react-native-onboarding-swiper": "^1.3.0",
    "react-native-paper": "^5.12.5",
    "react-native-reanimated": "^3.10.1",
    "react-native-reanimated-carousel": "^3.5.1",
    "react-native-safe-area-context": "4.10.5",
    "react-native-screens": "3.31.1",
    "react-native-stars": "^1.2.2",
    "react-native-vector-icons": "^10.2.0",
    "react-native-webview": "13.8.6",
    "react-native-zoomable-view": "^0.3.1",
    "react-query": "^3.39.3",
    "shorthash": "^0.0.2",
    "styled-components": "^6.0.4",
    "zustand": "^4.3.9"
  },
  "devDependencies": {
    "@babel/core": "^7.24.0",
    "@eslint/js": "^9.14.0",
    "eslint": "^8.57.1",
    "eslint-plugin-react": "^7.37.2",
    "globals": "^15.12.0"
  },
  "resolutions": {
    "@expo/config-plugins": "~8.0.0",
    "@expo/prebuild-config": "~7.0.0",
    "expo-modules-autolinking": "~1.11.0"
  },
  "private": true,
  "dev": "APP_VARIANT=development expo start"
}

[JohnnyBoySou]

• 1

[NOxDriver]

• 1

Are you having the same issue?

[szdziedzic]

Hey,

Can you send me the URL of your build?

[NOxDriver]

@szdziedzic

Hey,

Can you send me the URL of your build?

I sent you a message on Linkedin with the URL.

Thanks so much!

[szdziedzic]

I see this error in the expo doctor check of your project: Multiple lock files detected (yarn.lock, package-lock.json). This may result in unexpected behavior in CI environments, such as EAS Build, which infer the package manager from the lock file.

Can you try only to use one lock file?

[NOxDriver]

@szdziedzic

I see this error in the expo doctor check of your project: Multiple lock files detected (yarn.lock, package-lock.json). This may result in unexpected behavior in CI environments, such as EAS Build, which infer the package manager from the lock file.

Can you try only to use one lock file?

I updated it, and it's not showing that error, but it's still failing:

Running "expo doctor"
Running 14 checks on your project...
✔ Check package.json for common issues
✔ Check Expo config for common issues
✔ Check native tooling versions
✔ Check if the project meets version requirements for submission to app stores
✔ Check for common project setup issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for app config fields that may not be synced in a non-CNG project
✔ Check for issues with Metro config
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that packages match versions required by installed Expo SDK
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that native modules use compatible support package versions for installed Expo SDK

[NOxDriver]

Sentry was causing the issue. I fixed the Auth token and it worked.

[JohnnyBoySou]

What is Sentry?

[Jessie3]

Sentry was causing the issue. I fixed the Auth token and it worked.

Can you tell me how you solved this problem? i met the same question: Build failed: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.

[szdziedzic]

@Jessie3 it's usually best to inspect Xcode logs and look for error: logs there to find more info.