Build failed - "main.jsbundle does not exist" error when building iOS version with Expo SDK 49

[tej-thambi]

Summary

Build failing with Expo and React Native, there was a similar issue with the same title under SDK 48, but nothing from that has helped. Getting the following problem when doing eas build -p ios

❌ error: File /Users/expo/Library/Developer/Xcode/DerivedData/freeapp-celtkelekabrvocesclaslgcuhcp/Build/Intermediates.noindex/ArchiveIntermediates/freeapp/BuildProductsPath/Release-iphoneos/freeapp.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

It comes up during Run fastlane. My project does not have ios/ or android/ directories, or an index.js or metro config. I just used expo to start up the project in js.

Managed or bare workflow?

managed

What platform(s) does this occur on?

iOS

Package versions

No response

Environment

npx: installed 2 in 2.036s

expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.3.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 14.21.2 - ~/.nvm/versions/node/v14.21.2/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v14.21.2/bin/yarn
npm: 6.14.17 - ~/.nvm/versions/node/v14.21.2/bin/npm
Watchman: 2023.01.30.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.12.0 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9514443
Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild
npmPackages:
expo: ~49.0.8 => 49.0.9
react: 18.2.0 => 18.2.0
react-native: 0.72.4 => 0.72.4
npmGlobalPackages:
eas-cli: 5.2.0
expo-cli: 6.3.10
Expo Workflow: managed

Reproducible demo

#21542

Stacktrace (if a crash is involved)

No response

[expo-bot]

Hi there! It looks like your issue requires a minimal reproducible example, but it is invalid or absent. Please prepare such an example and share it in a new issue.

The best way to get attention to your issue is to provide a clean and easy way for a developer to reproduce the issue on their own machine. Please do not provide your entire project, or a project with more code than is necessary to reproduce the issue.

A side benefit of going through the process of narrowing down the minimal amount of code needed to reproduce the issue is that you may get lucky and discover that the bug is due to a mistake in your application code that you can quickly fix on your own.

Resources

• "How to create a Minimal, Reproducible Example"
• "How to narrow down the source of an error"

Common concerns

"I've only been able to reproduce it in private, proprietary code"

You may not have spent enough time narrowing down the root cause of the issue. Try out the techniques discussed in this manual debugging guide to learn how to isolate the problem from the rest of your codebase.

"I didn't have time to create one"

That's understandable, it can take some time to prepare. We ask that you hold off on filing an issue until you are able to fully complete the required fields in the issue template.

"You can reproduce it by yourself by creating a project and following these steps"

This is useful knowledge, but it's still valuable to have the resulting project that is produced from running the steps, where you have verified you can reproduce the issue.

[brentvatne]

https://docs.expo.dev/build-reference/troubleshooting/