question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The --device option fails on command line in v53.0

See original GitHub issue

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

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

Packages: (wanted => installed) react: 16.2.0 => 16.2.0 react-native: 0.53.0 => 0.53.0

Steps to Reproduce

  1. Initiate a new React Native project using react-native init projectName
  2. Run the command react-native run-ios --device deviceName

Expected Behavior

The app should have launched on my physical device. Additionally, if I already have an instance of Metro Bundler running using react-native start, it should just hook into that one and use that.

Actual Behavior

Metro Bundler opens and complains that Metro Bundler can't listen on port undefined. It then prompts the user to hit enter because the process has terminated. I’ve run into other random errors too. I’ve included one of those here as well.

Metro Bundler error 1 Metro Bundler error 2

Additionally, there is a lot of output in my main terminal about the Xcode build failing. I can include the full output in a comment below if requested.

Build error 1 Build error 2

Even if I try running an instance of Metro Bundler using react-native start before running react-native run-ios --device deviceName, it just starts a new instance in a new terminal window.

Reproducible Demo

You can reproduce this with a brand new project created using react-native init projectName.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:13
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
mlazaricommented, Mar 3, 2018

@Gulci Which version fixed the error? I have the same error with “react-native”: “0.54.0”. Running from Xcode works fine. The error appears only when I’m trying to run from the terminal with react-native run-ios --device="Mihai"

P.S. I found the fix https://github.com/facebook/react-native/pull/17983 It is included in 0.53.3, but not in 0.54.0

1reaction
gulcicommented, Mar 3, 2018

I’ll open the exact same issue. 😉

Read more comments on GitHub >

github_iconTop Results From Across the Web

The --device option fails on command line in v53.0 #17921
The following commit that came with the new release (v53.0) causes problems when the --device option is specified. The port is set to...
Read more >
Fix DiskPart I/O Device Error in Windows 10/8/7 - EaseUS
Diskpart wont complete command due to an I/O error? Receive DiskPart has encountered an error: the request could not be performed because of ......
Read more >
Command Line Interface Reference Guide - Cisco
This CLI guide provides CLI commands and guidelines for both the SG550XG product line and the Sx550X product line. Besides a few CLI...
Read more >
Version 4.3 Command Line Interface Reference Guide - Dell
the syntax details of command-line options that are used to configure BIOS settings for client systems. Topics: •. Running Dell Command | Configure...
Read more >
How to use the Regsvr32 tool and ... - Microsoft Support
Regsvr32 is a command-line utility to register and unregister OLE controls, such as DLLs and ActiveX controls in the Windows Registry.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found