Packager not starting after 0.59 to 0.60 migration #25585
Comments
react-native-bot
added
the
Tech: Bundler 📦
|
I'm seeing the same thing after upgrading from |
|
I am also having the same issue. The metro bundler doesn't start for ios or android after upgrading from 0.59.9 to 0.60.0. |
|
Facing same issue. The packager is running in iOS simulator but not running in android emulator or android device. The issue is after upgrading to 0.60. Created a new project with 0.60 and the issue still exists. |
|
Same Issue here. If I run react-native android metro doesnt boot up. I have to run react-native start then react-native run-android. However, If I run react-native ios metro pops boots up normally. |
|
Same here, any updates ? |
|
I've managed to know this (for iOS at least): the
|
|
@jacargentina it doesn't matter, it works on ios, run the project from xcode. |
|
Having this problem as well and continually get to where it says No bundle URL present any ideas how to get past this? No bundle popping up during build anymore either. |
|
Make sure you have "Start Packager" as one of the items on the Build Phases tab inside your Xcode project. I was having the exact same problem and I figured it out by comparing my Build Phases tab to a brand new project created on version 0.60.4 through export RCT_METRO_PORT="${RCT_METRO_PORT:=8081}"
echo "export RCT_METRO_PORT=${RCT_METRO_PORT}" > "${SRCROOT}/../node_modules/react-native/scripts/.packager.env"
if [ -z "${RCT_NO_LAUNCH_PACKAGER+xxx}" ] ; then
if nc -w 5 -z localhost ${RCT_METRO_PORT} ; then
if ! curl -s "http://localhost:${RCT_METRO_PORT}/status" | grep -q "packager-status:running" ; then
echo "Port ${RCT_METRO_PORT} already in use, packager is either not running or not running correctly"
exit 2
fi
else
open "$SRCROOT/../node_modules/react-native/scripts/launchPackager.command" || echo "Can't start packager automatically"
fi
fiNext time you run |
I did that at first and it did work OK but it would start the packager too late in the process and an error message would appear until I reloaded once the packager had finished bundling. I would recommend once you have done this that you move your new build phase (hold and drag in Build Phases tab) in between |
I've migrated my app from 0.59 to 0.60, and now somehow the "Start Packager" script in xcode is not running anything.
I've managed to get to the error which is
Unable to find application named 'Apple_Terminal' Can't start packager automaticallyReact Native version:
info Fetching system and libraries information...
System:
OS: macOS 10.14.5
CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 3.63 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.16.0 - /usr/local/bin/node
Yarn: 1.17.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
SDKs:
iOS SDK:
Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
Android SDK:
API Levels: 26, 27, 28
Build Tools: 27.0.3, 28.0.3, 29.0.0
System Images: android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
Android NDK: 19.2.5345600
IDEs:
Android Studio: 3.4 AI-183.5429.30.34.5452501
Xcode: 11.0/11M337n - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: ^0.60.0 => 0.60.0
Steps To Reproduce
Packager not starting.
Describe what you expected to happen:
Packager starting in a new terminal window, as it was on 0.59
Snack, code example, or link to a repository:
The text was updated successfully, but these errors were encountered: