New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Uncaught Error: Unsupported Bridge operation 0" on Electron's renderer devtools #344
Comments
I can't reproduce the bug you've reported by running the example repo, but it looks like you copied part of this repo and tried to run it as an electron app. That's not supported. It actually requires a fair bit of work (see PR #335). Once that PR has landed, a standalone version of v4 (running in Electron) will be available to support Safari and React Native. Actually, Safari support should mostly be there already if you'd like to check out the branch and build from source. Until that feature lands though, the Electron shell is not supported by this version. 😄 |
@bvaughn I'm not sure if I understood correctly - isn't #335 tracking Clarify, I am not trying to run current devtools as standalone. |
Installing the extension into an unsupported browser (anything but Chrome, Firefox, and Chromium Edge) is also not supported. The extension APIs aren't guaranteed to be the same. |
Repro steps
npm install && npm start
"Uncaught Error: Unsupported Bridge operation 0", source: chrome-extension://react-developer-tools/build/main.js (1)
localhost:8315
Descriptions
abc8ef3
of extension buildI am aware Electron is bit odd environment and probably experimental devtools have known glitches around, but couldn't figure out cause by myself and not successful to search existing issues.
Devtools simply doesn't work on Electron environment by throwing out
Unsupported Bridge operation 0
- not sure 1. what does0
actually means / 2. In what cases this could occur (Electron's devtools is nearly equivalent to Chromium devtools in most cases). Willing to dig deeper myself if I could have some clues or insights.The text was updated successfully, but these errors were encountered: