Skip to content

CLI fails when Chrome is not present #17787

Description

@neiker

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

Environment:
OS: macOS High Sierra 10.13.2
Node: 8.9.0
Yarn: Not Found
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: Not Found

Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.51.0 => 0.51.0

Steps to Reproduce

  1. Run npm start on a computer where chrome is not installed

Expected Behavior

Build flawless

Actual Behavior

Bundling `index.ios.js`  [development, non-minified]  ▓▓░░░░░░░░░░░░░░  13.7% (81/219)Launching Dev Tools...
Bundling `index.ios.js`  [development, non-minified]  ▓▓░░░░░░░░░░░░░░  14.4% (84/221)Google Chrome exited with error: Error: Exited with code 1
    at ChildProcess.<anonymous> (/Users/[user]/code/native-ios/node_modules/opn/index.js:86:8)
    at Object.onceWrapper (events.js:317:30)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Socket.stream.socket.on (internal/child_process.js:346:11)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at Pipe._handle.close [as _onclose] (net.js:554:12)

After I opened http://localhost:8081/debugger-ui/ on Firefox, it works correctly

Bundling `index.ios.js`  [development, non-minified]  100.0% (1328/1328), done.

Reproducible Demo

Just a fresh install

Activity

  1. gedeagas commented on Jan 31, 2018

    @gedeagas
    Contributor

    I think this is not a bug.

    This maybe happens because you once enable the debugging option on the specific emulator. So when you do npm start the debugging options is triggered.

    if you a init a new clean project and run npm start it should work flawlessly.

    Please correct me if I'm wrong.

  2. neiker commented on Feb 1, 2018

    @neiker
    Author

    Thanks for your answer, @gedeagas

    If this is so, where is saved that setting?
    My start script is just this:
    "start": "NODE_ENV='development' node node_modules/react-native/local-cli/cli.js start",

  3. react-native-bot commented on Feb 24, 2018

    @react-native-bot
    Collaborator

    Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

    I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

    How to Contribute • What to Expect from Maintainers

  4. added
    Ran CommandsOne of our bots successfully processed a command.
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Feb 24, 2018
  5. removed
    StaleThere has been a lack of activity on this issue and it may be closed soon.
    on Feb 24, 2018
  6. salmanwaheed commented on Feb 24, 2018

    @salmanwaheed
  7. salmanwaheed commented on Feb 24, 2018

    @salmanwaheed
  8. locked as resolved and limited conversation to collaborators on Feb 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Ran CommandsOne of our bots successfully processed a command.Resolution: LockedThis issue was locked by the bot.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions