0.63 upgrade results in a bundle that never finishes building

[djMax]

Please provide all the information requested. Issues that do not follow this format are likely to stall.

Description

I can no longer build a react bundle, it gets to "Done copying assets" and then never finishes.

React Native version:

info Fetching system and libraries information...
System:
    OS: macOS 10.15.5
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 813.83 MB / 32.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.17.0 - ~/.nvm/versions/node/v12.17.0/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v12.17.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.0
      System Images: android-29 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.0 AI-193.6911.18.40.6514223
    Xcode: 11.5/11E608c - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_231 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: 0.63.0 => 0.63.0
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce

I'm not sure I can reliably repro this, so I probably need some steps that might yield more data. But I run this:

npx react-native bundle --platform ios --entry-file index.js --dev false --bundle-output ./ios/main.jsbundle --assets-dest ./ios --sourcemap-output ./sourcemap.js

Also, in case it's relevant, I have a monorepo setup with yarn workspaces and lerna.

Expected Results

A bundle should be produced in something less than an hour, which is how long I waited...

[djMax]

A little more info - this has something to do with a custom metro transformer I have written to do localization. Even if I reduce it to this:

const upstreamTransformer = require('metro-react-native-babel-transformer');

module.exports.transform = function transform({ src, filename, options }) {
  return upstreamTransformer.transform({ src, filename, options });
};

It will hang.

[voidrender]

I'm also facing issues with the bundler on 0.63 in two projects, but it might be a slightly different issue because I'm promptly getting errors while bundling for release. One is a yarn workspaces / Lerna monorepo, but the other is not. Both use babel-plugin-module-resolver to resolve modules using shortened absolute paths. The release notes don't seem to have much in the way of bundler changes, but the same config bundles just fine on 0.62.2. Has anyone come across any changes relevant to bundling in 0.63.0?

The closest I've found to what I'm experiencing is being discussed in this StackOverflow question, in case any of this is useful for you.

[sharifhh]

Change your babel.config.js to .babelrc.js and it will work

[typester]

I have the same issue to @ioveracker's, not sure it's the same as the original issue of this thread though.

With 0.63 and babel-plugin-module-resolver, it seems that jsbundle won't created from ./ios directory (where Xcode execute react-native scripts). It works on root directory of the react-native project though.

So I did a temporary quick fix to add cd $PROJECT_DIR/.. before the "$NODE_BINARY" $NODE_ARGS "$CLI_PATH" $BUNDLE_COMMAND \ line on node_modules/react-native/scripts/react-native-xcode.sh

I don't know why this is happened, and hope will fix soon!

[voidrender]

@typester good call! That works! 🎉 To be clear, in my case, rather than patch node_modules/react-native/scripts/react-native-xcode.sh, I added cd $PROJECT_DIR/.. to the first line of the Bundle React Native code and images Build Phase in Xcode. I.e.:

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

[makarkotlov]

I'm also facing issues with the bundler on 0.63 in two projects, but it might be a slightly different issue because I'm promptly getting errors while bundling for release. One is a yarn workspaces / Lerna monorepo, but the other is not. Both use babel-plugin-module-resolver to resolve modules using shortened absolute paths. The release notes don't seem to have much in the way of bundler changes, but the same config bundles just fine on 0.62.2. Has anyone come across any changes relevant to bundling in 0.63.0?

The closest I've found to what I'm experiencing is being discussed in this StackOverflow question, in case any of this is useful for you.

same, in my case bundler can't resolve files with absolute path, but it works on 0.62.2, weird

[SimoneCarnio]

I'm also using babel-plugin-module-resolver and I fixed this issue by removing from my .bablerc.js this line:

cwd: 'babelrc',

[todorone]

Unfortunately, cd $PROJECT_DIR/.. doesn't work with SENTRY setup as it has own script layer over react-native-xcode.sh... 😿

[deserthurricane]

I have this issue while archiving app in XCode for distribution to AppStore. When I'm in debug mode - everything works fine.
For me the solution of @ioveracker worked for the archive build, but I'm looking forward to a new patch release of RN to fix this issue.

[maxvw]

Unfortunately, cd $PROJECT_DIR/.. doesn't work with SENTRY setup as it has own script layer over react-native-xcode.sh... 😿

@todorone This version worked for us with Sentry using the workaround @typester previously mentioned;

cd $PROJECT_DIR/..
export SENTRY_PROPERTIES=ios/sentry.properties
export NODE_BINARY=$(which node)
./node_modules/@sentry/cli/bin/sentry-cli react-native xcode ./node_modules/react-native/scripts/react-native-xcode.sh