react-native: Build App IOS ERROR
Description
2 days ago when I built it it was normal, but now when I build it there is an error
Run fastlanne : Generating debug ReliposSaleOrder » ReliposSaleOrder.app.dSYM
› Executing ReliposSaleOrder » Bundle React Native code and images
the transform cache was reset.
❌ error: File /Users/expo/Library/Developer/Xcode/DerivedData/ReliposSaleOrder-ewdmlwntzptsgbdugffzlcepqjhl/Build/Intermediates.noindex/ArchiveIntermediates/ReliposSaleOrder/BuildProductsPath/Release-iphoneos/ReliposSaleOrder.app/main.jsbundle does not exist. This must be a bug with React Native, please report it here: https://github.com/facebook/react-native/issues
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')
▸ ** ARCHIVE FAILED **
▸ The following build commands failed:
▸ PhaseScriptExecution Bundle\ React\ Native\ code\ and\ images /Users/expo/Library/Developer/Xcode/DerivedData/ReliposSaleOrder-ewdmlwntzptsgbdugffzlcepqjhl/Build/Intermediates.noindex/ArchiveIntermediates/ReliposSaleOrder/IntermediateBuildFilesPath/ReliposSaleOrder.build/Release-iphoneos/ReliposSaleOrder.build/Script-00DD1BFF1BD5951E006B06BC.sh (in target ‘ReliposSaleOrder’ from project ‘ReliposSaleOrder’)
▸ (1 failure)
** ARCHIVE FAILED **
The following build commands failed:
PhaseScriptExecution Bundle\ React\ Native\ code\ and\ images /Users/expo/Library/Developer/Xcode/DerivedData/ReliposSaleOrder-ewdmlwntzptsgbdugffzlcepqjhl/Build/Intermediates.noindex/ArchiveIntermediates/ReliposSaleOrder/IntermediateBuildFilesPath/ReliposSaleOrder.build/Release-iphoneos/ReliposSaleOrder.build/Script-00DD1BFF1BD5951E006B06BC.sh (in target 'ReliposSaleOrder' from project 'ReliposSaleOrder')
(1 failure)
React Native Version
0.70.14
Output of npx react-native info
System: OS: macOS 12.6.8 CPU: (8) x64 Intel® Core™ i7-4980HQ CPU @ 2.80GHz Memory: 39.93 MB / 16.00 GB Shell: 5.8.1 - /bin/zsh Binaries: Node: 18.18.0 - /usr/local/bin/node Yarn: Not Found npm: 9.8.1 - /usr/local/bin/npm Watchman: Not Found Managers: CocoaPods: Not Found SDKs: iOS SDK: Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1 Android SDK: Not Found IDEs: Android Studio: Not Found Xcode: 14.2/14C18 - /usr/bin/xcodebuild Languages: Java: Not Found npmPackages: @react-native-community/cli: Not Found react: 18.1.0 => 18.1.0 react-native: 0.70.14 => 0.70.14 react-native-macos: Not Found npmGlobalPackages: react-native: Not Found
Steps to reproduce
eas build --platform ios
Snack, screenshot, or link to a repository
About this issue
- Original URL
- State: closed
- Created 8 months ago
- Reactions: 3
- Comments: 22 (1 by maintainers)
it looks like there was a regression in a patch release of react-native 0.70 between 0.70.9 and 0.70.14, so i rolled back the recommended version to 0.70.8 for Expo SDK 47. that should resolve the issue.
the problem appears to be that on react-native 0.70.14, specifying the
hermes_enabledproperty in the Podfile is insufficient, and it also looks for aUSE_HERMESenvironment variable, and if that is not defined, then it assumes you are using hermes.this fixed it for me: https://docs.expo.dev/guides/using-hermes/#using-sdk-47-or-lower
@Minh-ka This worked for me - thank you so much. We’re getting ready to launch our product and I’ve been at a standstill for two days on this issue! Thank you! 👏
Help me Pls
Yes, am seeing the same after upgrading to 0.70.14 from 0.70.8.
@firasrg - correct, you can just run a new build. we reverted the recommend react-native version for sdk 47 from 0.70.14 to 0.70.8, so we no longer pull in the commit from react-native that caused this regression
i have the same error too.
Also seeing the same exact issue
Managed to build today without changing anything.
If you are using Expo, please open an issue in their repo, not in React Native one. They will be better equipped to answer your question.
same issue