Unable to run iOS on Device from Command Line - Simulator Works. RCT_METRO_PORT undefined #18525

justinwaite · 2018-03-23T19:04:14Z

I have reviewed the documentation
I have searched existing issues
I am using the latest React Native version

I am unable to run my app on my iOS device via the command react-native run-ios --device. I am able to run it on the simulator via react-native run-ios and I am able to open the XCode project and run on my device directly from the project. When compiling, I receive the following error:

/Users/justin/VSCodeProjects/MyApp/node_modules/react-native/React/Base/RCTBundleURLProvider.m:17:53: error: use of undeclared identifier 'undefined'; did you mean 'underline'?
const NSUInteger kRCTBundleURLProviderDefaultPort = RCT_METRO_PORT;
                                                    ^~~~~~~~~~~~~~
                                                    underline
In file included from <built-in>:359:
<command line>:5:24: note: expanded from here
#define RCT_METRO_PORT undefined

Just from that message, it appears that RCT_METRO_PORT is undefined and causing the build to fail while using the command line to run the app on iOS on my device.

I have googled this error and nothing has come up to this point. Any ideas?

Environment

Environment:
  OS: macOS High Sierra 10.13.3
  Node: 8.9.3
  Yarn: Not Found
  npm: 5.7.1
  Watchman: 4.9.0
  Xcode: Xcode 9.2 Build version 9C40b
  Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)
  react: 16.3.0-alpha.1 => 16.3.0-alpha.1
  react-native: 0.54.2 => 0.54.2

Steps to Reproduce

You can clone my repository and try out the command react-native run-ios --device.

Expected Behavior

I expected that it would run on my device.

Actual Behavior

Build fails with an error described above.

The text was updated successfully, but these errors were encountered:

hramos · 2018-03-23T19:34:50Z

RCT_METRO_PORT was added in 33d710e#diff-0822d6820d37285597b7a89988c8aea1 and it looks like someone else noticed the same behavior back then.

The author of the PR that culminated in that commit is @DaKaZ. It looks like they left a comment on the PR that may help (see #16172).

@DaKaZ is there any way we can prevent people from running into this issue?

DaKaZ · 2018-03-23T20:16:13Z

Hmmm, I am not entirely sure. I guess I always use Xcode to run on device so I had not run into this. A short term fix is likely andding RCT_METRO_PORT as an env var:

RCT_METRO_PORT=8081 react-native run-ios --device

I'll try to look into this more

justinwaite · 2018-03-23T20:31:26Z

@hramos, @DaKaZ, thanks for your quick replies. @DaKaZ unfortunately running RCT_METRO_PORT=8081 react-native run-ios --device did not work. Same error is called. I looked up a bit higher in the console logs and noticed this as well. Not sure if it is related, but it referenced ports so I thought maybe it has something to do with it as well:

PhaseScriptExecution Start\ Packager /Users/me/projects/MyApp/ios/build/Build/Intermediates.noindex/React.build/Debug-iphoneos/React.build/Script-006B79A01A781F38006873D1.sh
    cd /Users/me/projects/MyApp/node_modules/react-native/React
    /bin/sh -c /Users/me/projects/MyApp/ios/build/Build/Intermediates.noindex/React.build/Debug-iphoneos/React.build/Script-006B79A01A781F38006873D1.sh

nc: port range not valid

b45ch1 · 2018-03-24T10:14:32Z

I can confirm that react-native run-ios --device does not work on react-native version 0.54.2
As workaround, this works for me:
ios-deploy -c
to get the udid of my phone and then use
react-native run-ios --udid e0452************************************
to compile and deploy the project to the phone.

To fix the issue, I believe one has to adapt the function runOnDevice(...) in file node_modules/react-native/local-cli/runIOS/runIOS.js and make it consistent with runOnDeviceByUdid(...) and runOnSimulator(...).

justinwaite · 2018-03-27T06:03:19Z

@b45ch1 Unfortunately for me, running by uuid is still not working. I receive the same build error of RCT_METRO_PORT being undefined.

lizeqing · 2018-03-30T03:01:14Z

seens it happen on https://github.com/facebook/react-native/blob/master/local-cli/runIOS/runIOS.js#L130:5 , just missing the port argument for buildProject function.

Simply add args.port at end of buildProject calling, it will work

gianpaj · 2018-03-30T15:15:34Z

@lizeqing 's workaround does work. tested on 0.54.4

stdavis · 2018-03-30T18:03:01Z

Looks like this issue was fixed in: #17983 and should be in 0.55.

But no backport to 0.54. :(

justinwaite · 2018-03-30T18:54:46Z

@stdavis Thanks for pointing this out, looks like we'll just have to wait for 0.55! That is manageable. VSCode's RN plugin seems to rely on ios-deploy, so you can create a debug configuration like so:

    {
      "name": "Debug iOS Device",
      "program": "${workspaceRoot}/.vscode/launchReactNative.js",
      "type": "reactnative",
      "request": "launch",
      "platform": "ios",
      "sourceMaps": true,
      "outDir": "${workspaceRoot}/.vscode/.react",
      "target": "device"
    },

jaygould · 2018-04-03T20:37:27Z

Just installed 0.55.0 and it's still happening, can anyone else confirm?

ASteinheiser · 2018-04-04T00:38:57Z

Yes, try downgrading to react-native: 0.52.2, seems to have solved it for a few of us.

chitezh · 2018-04-06T17:11:10Z

@hramos This is still happening, why was it closed?

dylanneild · 2018-04-06T20:08:59Z

0.55.0 also seems to break IntelliJ Idea based projects.

With 0.54.0 and earlier, running a project launches react-native-start which starts Metro on 8081, then in another run window, launches the command line Xcode build for the current project (if necessary), launches an iOS simulator, installs the new Xcode build, and then starts the app (which loads from Metro).

0.55.0 breaks this behaviour. In addition to the above RCT_METRO_PORT bug that breaks the Xcode command line build process, react-native-start now seems to try to start a second Metro process in a Terminal.app window that can't start (undefined port).

Reverting to 0.54.0 is fine, though.

Anyone else seeing this?

Axbon · 2018-04-09T15:01:38Z

Yup, we experience the same issue in 0.55 , same as #18673

getaaron · 2018-04-12T19:28:47Z

I am also experiencing this on 0.55. Here is my react-native info output in case that helps:

Environment:
  OS: macOS High Sierra 10.13.3
  Node: 9.5.0
  Yarn: 1.3.2
  npm: 5.6.0
  Watchman: 4.9.0
  Xcode: Xcode 9.2 Build version 9C40b
  Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)
  react: ^16.3.0-alpha.1 => 16.3.0-alpha.3
  react-native: 0.55.0 => 0.55.0

duro · 2018-04-20T19:43:29Z

I am also getting this problem, but I don't see any specific error coming out of the logs when app crashes. That said, launching from XCode works just fine. But app crashes immediately when launching from CLI.

grabvinod · 2018-04-25T09:21:41Z

I am still facing this issue on 0.55.0. Can anyone confirm if this is being fixed or fixed already or any work around.

gonzaloreciog · 2018-05-04T10:24:06Z

We're having this issue as well, any update or fix on this? thanks!

omatrot · 2018-05-09T08:40:21Z

This issue is really affecting my development workflow as I'm running on a MacBook Air with limited disk space. Installing XCode is not an option.

fadeojo · 2018-05-10T02:26:24Z

Any word on a work around for this issue?

justinwaite · 2018-05-10T02:57:47Z

Personally I started using Expo as much as possible to avoid having to use the react native CLI to run projects. @omatrot this also does not require you to have XCode installed; I understand that Expo does not work for every project, but they have a lot of built-in native libraries now that I feel are able to solve most normal app needs.

getaaron · 2018-05-10T04:00:06Z

@fadeojo the only workarounds I know are to use expo or run your app from Xcode

omatrot · 2018-05-12T06:08:20Z

Upgrading to 0.55.0 did it for me. phew...

Environment:
OS: macOS High Sierra 10.13.4
Node: 8.9.3
Yarn: Not Found
npm: 5.8.0
Watchman: 4.9.0
Xcode: Not Found
Android Studio: Not Found

Packages: (wanted => installed)
react: ^16.3.1 => 16.3.2
react-native: ^0.55.0 => 0.55.4

omatrot · 2018-05-29T16:28:54Z

Well on another Mac computer I have the problem with .0.55
And It does not compile with XCode /!
So basically I'm stuck with this particular machine.

Environment:
OS: macOS High Sierra 10.13.4
Node: 8.11.2
Yarn: 1.2.0
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.3.1 Build version 9E501
Android Studio: 3.1 AI-173.4720617

Packages: (wanted => installed)
react: ^16.3.0-alpha.0 => 16.3.2
react-native: 0.55.0 => 0.55.0

flyingxu · 2018-05-30T06:08:07Z

    "react": "^16.4.0",
    "react-native": "^0.55.4",

fixed the issue for me

omatrot · 2018-05-30T09:19:23Z

@flyingxu Yep same here :)

vinicarra · 2018-06-19T02:31:59Z

Same issue here, the application builds with react-native run-ios but it instantly crash when it starts - the bundler created from npm start doesn't ever connect to the application. However if I build the application directly from Xcode it successfully builds and opens but I want to use the react-native-cli in the building process due to some specefic debugging tools.

Environment:
OS: macOS High Sierra 10.13.5
Node: 8.11.3
Yarn: Not Found
npm: 5.6.0
Watchman: Not Found
Xcode: Xcode 9.4.1 Build version 9F2000
Android Studio: Not Found

Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: 0.55.4 => 0.55.4

acoulon99 · 2018-06-22T15:01:05Z

Similar to @flyingxu 's solution, this fixed it for me. Note the difference in react version.

"react": "^16.3.1",
"react-native": "^0.55.4",

santomegonzalo · 2018-07-09T09:59:06Z

Similar to @flyingxu and @acoulon99 ... the new version 0.55.4 will fix the error

    "react": "16.3.1",
    "react-native": "0.55.4",

Monte9 · 2018-09-21T22:06:43Z

I didn't want to upgrade my RN version so @b45ch1 solution worked great! 🌮

vincentvella · 2018-10-31T19:15:11Z

If you're trying to run it from an npm script instead of just the react-native run-ios you'll have to run the command like:
npm run ios -- --udid e0452************************************
-or-
npm run ios -- --simulator="iPhone (whatever)"

dkfl1995 · 2018-11-27T14:17:10Z

Hmmm, I am not entirely sure. I guess I always use Xcode to run on device so I had not run into this. A short term fix is likely andding RCT_METRO_PORT as an env var:
RCT_METRO_PORT=8081 react-native run-ios --device
I'll try to look into this more

This really work, but dear hater-guys I'm longing to tell you that somewhat this command doesnt work - shell says that it is uncapable to install app to device.
Yes. If (error) shell will ask you to install "npm i -g ios-deploy"... Try 't!
I install of ios-deploy finishes with error (what I had been faced with) run following shell command npm i -g ios-deploy --unsafe-perms=true or even not recommended sudo npm i -g ios-deploy --unsafe-perms=true...
thus all is done run RCT_METRO_PORT=8081 react-native run-ios --device like @jdeanwaite said above...
You can change or remove RCT_METRO_PORT argument (removed argument defaults to :8081).

react-native-bot added Platform: iOS iOS applications. Platform: macOS Building on macOS. labels Mar 23, 2018

hramos added Help Wanted Issues ideal for external contributors. 💻CLI labels Mar 23, 2018

whitedogg13 mentioned this issue Mar 28, 2018

ios build failed revtel/react-native-nfc-manager#41

Closed

hramos removed the Platform: macOS Building on macOS. label Mar 29, 2018

justinwaite closed this as completed Mar 30, 2018

zen0wu mentioned this issue Apr 4, 2018

[0.55.0] Metro Bundler can't listen on port undefined #18681

Closed

3 tasks

justinwaite reopened this Apr 6, 2018

react-native-bot added the ⏪Old Version label May 16, 2018

hramos closed this as completed Aug 8, 2018

facebook locked as resolved and limited conversation to collaborators Aug 8, 2019

react-native-bot added the Resolution: Locked This issue was locked by the bot. label Aug 8, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to run iOS on Device from Command Line - Simulator Works. RCT_METRO_PORT undefined #18525

Unable to run iOS on Device from Command Line - Simulator Works. RCT_METRO_PORT undefined #18525

justinwaite commented Mar 23, 2018 •

edited

Loading

hramos commented Mar 23, 2018

DaKaZ commented Mar 23, 2018

justinwaite commented Mar 23, 2018 •

edited

Loading

b45ch1 commented Mar 24, 2018

justinwaite commented Mar 27, 2018

lizeqing commented Mar 30, 2018

gianpaj commented Mar 30, 2018 •

edited

Loading

stdavis commented Mar 30, 2018 •

edited

Loading

justinwaite commented Mar 30, 2018 •

edited

Loading

jaygould commented Apr 3, 2018

ASteinheiser commented Apr 4, 2018

chitezh commented Apr 6, 2018

dylanneild commented Apr 6, 2018

Axbon commented Apr 9, 2018

getaaron commented Apr 12, 2018

duro commented Apr 20, 2018

grabvinod commented Apr 25, 2018

gonzaloreciog commented May 4, 2018

omatrot commented May 9, 2018

fadeojo commented May 10, 2018

justinwaite commented May 10, 2018

getaaron commented May 10, 2018

omatrot commented May 12, 2018

omatrot commented May 29, 2018

flyingxu commented May 30, 2018

omatrot commented May 30, 2018

vinicarra commented Jun 19, 2018 •

edited

Loading

acoulon99 commented Jun 22, 2018

santomegonzalo commented Jul 9, 2018

Monte9 commented Sep 21, 2018

vincentvella commented Oct 31, 2018

dkfl1995 commented Nov 27, 2018 •

edited

Loading

Unable to run iOS on Device from Command Line - Simulator Works. RCT_METRO_PORT undefined #18525

Unable to run iOS on Device from Command Line - Simulator Works. RCT_METRO_PORT undefined #18525

Comments

justinwaite commented Mar 23, 2018 • edited Loading

Environment

Steps to Reproduce

Expected Behavior

Actual Behavior

hramos commented Mar 23, 2018

DaKaZ commented Mar 23, 2018

justinwaite commented Mar 23, 2018 • edited Loading

b45ch1 commented Mar 24, 2018

justinwaite commented Mar 27, 2018

lizeqing commented Mar 30, 2018

gianpaj commented Mar 30, 2018 • edited Loading

stdavis commented Mar 30, 2018 • edited Loading

justinwaite commented Mar 30, 2018 • edited Loading

jaygould commented Apr 3, 2018

ASteinheiser commented Apr 4, 2018

chitezh commented Apr 6, 2018

dylanneild commented Apr 6, 2018

Axbon commented Apr 9, 2018

getaaron commented Apr 12, 2018

duro commented Apr 20, 2018

grabvinod commented Apr 25, 2018

gonzaloreciog commented May 4, 2018

omatrot commented May 9, 2018

fadeojo commented May 10, 2018

justinwaite commented May 10, 2018

getaaron commented May 10, 2018

omatrot commented May 12, 2018

omatrot commented May 29, 2018

flyingxu commented May 30, 2018

omatrot commented May 30, 2018

vinicarra commented Jun 19, 2018 • edited Loading

acoulon99 commented Jun 22, 2018

santomegonzalo commented Jul 9, 2018

Monte9 commented Sep 21, 2018

vincentvella commented Oct 31, 2018

dkfl1995 commented Nov 27, 2018 • edited Loading

justinwaite commented Mar 23, 2018 •

edited

Loading

justinwaite commented Mar 23, 2018 •

edited

Loading

gianpaj commented Mar 30, 2018 •

edited

Loading

stdavis commented Mar 30, 2018 •

edited

Loading

justinwaite commented Mar 30, 2018 •

edited

Loading

vinicarra commented Jun 19, 2018 •

edited

Loading

dkfl1995 commented Nov 27, 2018 •

edited

Loading