Windows: Chrome control fails with nodeRepl.fetch request failed
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Chrome browser control fails on Windows with nodeRepl.fetch request failed.
Chrome was detected, but listing tabs failed. In-app browser tab listing succeeded in the same session. An attempt to open Edge through the control tool also failed.
Extension and native-host checks passed. Reinstalling the extension, restarting Windows and the app, and resetting the browser session did not resolve the issue. The app reports it is up to date.
Feedback ID: 01a07aca-9ad6-71d1-92ed-383061a55e95
Please advise on the underlying cause and a supported fix or workaround.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported Windows failure, Feedback ID 01a07aca-9ad6-71d1-92ed-383061a55e95, and the nodeRepl.fetch request failed message. Compare Chrome tab listing with the successful in-app listing and the failed Edge attempt; done means identifying the underlying cause and documenting a supported fix or workaround.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100