expo icon indicating copy to clipboard operation
expo copied to clipboard

Unable to generate app.manifest for expo-updates

Open mogusbi opened this issue 2 years ago • 5 comments

Summary

I am unable to build an iOS app because of the following error;

[RUN_FASTLANE] ▸ ** ARCHIVE FAILED **
[RUN_FASTLANE] ▸ The following build commands failed:
[RUN_FASTLANE] ▸        PhaseScriptExecution [CP-User]\ Generate\ app.manifest\ for\ expo-updates /Users/mo/Library/Developer/Xcode/DerivedData/TestApp-bsuywqhkqfodtcfgxuayjmcyvhpt/Build/Intermediates.noindex/ArchiveIntermediates/TestApp/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/EXUpdates.build/Script-46EB2E00027960.sh (in target 'EXUpdates' from project 'Pods')

This only appears to be an issue with iOS, the Android build is able to run without any errors. I can only get the iOS app to build if I uninstall expo-updates.

What platform(s) does this occur on?

iOS

SDK Version

50.0.11

Environment

expo-env-info 1.2.0 environment info: System: OS: macOS 14.2.1 Shell: 5.9 - /bin/zsh Binaries: Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node Yarn: 4.1.1 - ~/.nvm/versions/node/v18.15.0/bin/yarn npm: 9.7.2 - ~/xxx/xxx/xxx/node_modules/.bin/npm Managers: CocoaPods: 1.11.3 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: DriverKit 23.4, iOS 17.4, macOS 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4 IDEs: Android Studio: 2023.1 AI-231.9392.1.2311.11330709 Xcode: 15.3/15E204a - /usr/bin/xcodebuild Expo Workflow: managed

Minimal reproducible example

https://github.com/mogusbi/expo-updates-monorepo

Running the following command. Mobile app is inside of a Yarn Berry workspace and I have a ENTRY_FILE env var pointing to the entry file, which is ./applications/mobile/src/App.tsx.

yarn workspace @application/mobile eas build --non-interactive --platform ios --local

mogusbi avatar Mar 14 '24 10:03 mogusbi

I was facing the same issue, I updated @expo/cli to 0.17.7 and now it works fine. Do not know how come it can be related.

nlarif avatar Mar 14 '24 21:03 nlarif

Same error occurs after downgrading to @expo/[email protected]. It also appears to completely ignore the ENTRY_FILE environment variable and defaults to index.js as the entry point of the app

mogusbi avatar Mar 15 '24 09:03 mogusbi

@mogusbi I had spent more than 5 days on it. It is related to a check on 'based on dependency analysis' in build phase setting on code. But wasn't able to continue with the eas build after that and switched to code and testflight

agrittiwari avatar Apr 08 '24 15:04 agrittiwari

same here run with expo v50 and expo-updates v 0.25.14

similar error occurs

[RUN_FASTLANE] ▸ The following build commands failed:
[RUN_FASTLANE] ▸ 	PhaseScriptExecution [CP-User]\ Generate\ updates\ resources\ for\ expo-updates /Users/nikechan/Library/Developer/Xcode/DerivedData/popbeeprodpreview-demvgkthwgcnjicqlmfpgarrjtff/Build/Intermediates.noindex/ArchiveIntermediates/popbeeprodpreview/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/EXUpdates.build/Script-46EB2E000480A0.sh (in target 'EXUpdates' from project 'Pods')

nikechanhk avatar May 20 '24 08:05 nikechanhk

It seems that it only happen if NODE_ENV is set to production

nikechanhk avatar May 20 '24 13:05 nikechanhk

This issue is stale because it has been open for 90 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

github-actions[bot] avatar Aug 18 '24 14:08 github-actions[bot]

This has still not been resolved

mogusbi avatar Aug 18 '24 14:08 mogusbi

same issue

mrevanzak avatar Sep 10 '24 01:09 mrevanzak

This issue is stale because it has been open for 90 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

github-actions[bot] avatar Dec 09 '24 02:12 github-actions[bot]

This has still not been resolved.

mogusbi avatar Dec 09 '24 09:12 mogusbi

I got the same error when building for iOS production. Using expo v50 and expo-updates v 0.25.14 as well.

srsly4 avatar Jan 08 '25 18:01 srsly4

Identical error to @nikechanhk . expo-updates: 0.25.28. expo: 51.0.38 Is anyone able to triage?

tj-mc avatar Mar 26 '25 03:03 tj-mc

In our case, we resolved this issue by setting

    env:
      NODE_OPTIONS: --max_old_space_size=4096

In each github action that calls node (basically all). Not sure how it works for EAS users. We also used a larger runner, and that seemed to help.

tj-mc avatar Mar 31 '25 05:03 tj-mc