Skip to content

Does not reuse tab from Google Chrome Dev and Google Chrome Beta when starting #12411

Closed
@nvh95

Description

Describe the bug

On MacOS, if the users have both Google Chrome and Google Chrome Dev installed, but they have only Google Chrome Dev opened. Then, startBrowserProcess will not reuse the opening tab in Google Chrome Dev, but open a new tab in Google Chrome.

This happens with Google Chrome Beta as well, but not Google Chrome Canary (since it's already in the list).

I did create a PR to fix this (#12412)

Reproducible demo

Screen.Recording.2022-05-19.at.01.16.40.mov

Environment

Click to expand!

Environment Info:

current version of create-react-app: 5.0.1
running from /Users/somewhere/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app

System:
OS: macOS 12.0.1
CPU: (8) arm64 Apple M1
Binaries:
Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
Yarn: 1.22.15 - ~/.nvm/versions/node/v16.15.0/bin/yarn
npm: 8.5.5 - ~/.nvm/versions/node/v16.15.0/bin/npm
Browsers:
Chrome: 101.0.4951.64
Edge: Not Found
Firefox: Not Found
Safari: 15.1
npmPackages:
react: ^18.1.0 => 18.1.0
react-dom: ^18.1.0 => 18.1.0
react-scripts: 5.0.1 => 5.0.1
npmGlobalPackages:
create-react-app: Not Found

Steps to reproduce

(Write your steps here:)

  1. Have both Google Chrome and Google Chrome Dev installed
  2. Open only Google Chrome Dev
  3. Run react-scripts start

Expected behavior

App (http://localhost:3000) should open in Google Chrome Dev

Actual behavior

A new instance of Google Chrome is created and app (http://localhost:3000) is opened in a new tab in Google Chrome

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions