Open SantiagoChiappe opened 3 months ago
@SantiagoChiappe are you getting an error similar to this (reported in https://github.com/electron/electron/issues/37876#issuecomment-1984873828) in your main process?
[91044:0308/100700.690484:ERROR:CONSOLE(2)] "Electron sandboxed_renderer.bundle.js script failed to run", source: node:electron/js2c/sandbox_bundle (2)
[91044:0308/100700.690537:ERROR:CONSOLE(2)] "TypeError: object null is not iterable (cannot read property Symbol(Symbol.iterator))", source: node:electron/js2c/sandbox_bundle (2)
@SantiagoChiappe are you getting an error similar to this (reported in #37876 (comment)) in your main process?
[91044:0308/100700.690484:ERROR:CONSOLE(2)] "Electron sandboxed_renderer.bundle.js script failed to run", source: node:electron/js2c/sandbox_bundle (2) [91044:0308/100700.690537:ERROR:CONSOLE(2)] "TypeError: object null is not iterable (cannot read property Symbol(Symbol.iterator))", source: node:electron/js2c/sandbox_bundle (2)
Yes I do, only when opening devtools. I also got other errors when I reload the app using View -> Reload, but then react devtools appear as I mentioned previously :
[1] [73616:0410/004950.275:ERROR:CONSOLE(1)] "uniqueContextId not found", source: devtools://devtools/bundled/core/sdk/sdk.js (1)
[1] [73616:0410/004950.275:ERROR:CONSOLE(1)] "Extension server error: Inspector protocol error: uniqueContextId not found", source: devtools://devtools/bundled/models/extensions/extensions.js (1)
[1] [73616:0410/004950.278:ERROR:CONSOLE(1)] "Received error with code E_PROTOCOLERROR while checking if react has loaded: "Inspector protocol error: %s"", source: chrome-extension://deachpobkibmlfmamelbofgimdagiiob/build/main.js (1)```
Got the same issue
Exact same issue but with Vue devtools with the exception that it will not load even after reloading. Same error when trying to open devtools.
[24844:0422/101748.810:ERROR:CONSOLE(1)] "Request Autofill.enable failed. {"code":-32601,"message":"'Autofill.enable' wa
sn't found"}", source: devtools://devtools/bundled/core/protocol_client/protocol_client.js (1)
[24844:0422/101748.903:ERROR:CONSOLE(2)] "Electron renderer.bundle.js script failed to run", source: node:electron/js2c/
renderer_init (2)
[24844:0422/101748.903:ERROR:CONSOLE(2)] "TypeError: object null is not iterable (cannot read property Symbol(Symbol.ite
rator))", source: node:electron/js2c/renderer_init (2)
Any update on this? how to resolve the issue?
Resolved this by using the react-devtools
package instead of installing the chrome extension.
yarn add --dev react-devtools
"dev:react-devtools": "react-devtools"
or something like that to the scripts in the package.json<script src="http://localhost:8097"></script>
to the dev version of your renderer index html fileyarn run dev:react-devtools
it will launch the react-devtools server and make the react devtools available in the app window devtools.Resolved this by using the
react-devtools
package instead of installing the chrome extension.
- Exec
yarn add --dev react-devtools
- Add
"dev:react-devtools": "react-devtools"
or something like that to the scripts in the package.json- Add
<script src="http://localhost:8097"></script>
to the dev version of your renderer index html file- Now when you exec
yarn run dev:react-devtools
it will launch the react-devtools server and make the react devtools available in the app window devtools.
It's workable on my project. Thanks.
Preflight Checklist
Electron Version
29.1.4
What operating system are you using?
Windows
Operating System Version
Windows 11 Home 23H2
What arch are you using?
x64
Last Known Working Electron version
No response
Expected Behavior
When I launch my Electron app on developer mode, React Devtools are installed and attached to my app.
Actual Behavior
React Devtools are installed, but not attached to my app. A manual reload or force reload is required to attach it. Same problem if I installed React Devtools manually from Chrome extensions, have to reload manually.
Testcase Gist URL
No response
Additional Information
My code :
I tried also reloading the window on my code or adding a timer to reload the window but without success.