-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
setupMetamask Errors with Electron #188
Comments
Call stack
|
Yeah only getting 1 page showing up in
I'd expect to see metamask extension popping up here. Although I'm still figuring out if Electron actually supports metamask in the first place. |
Hey @marcusnewton, after a quick look I can see that synpress could support Electron (as Electron supports loading Chrome extensions which would be metamask in this case), but it would require more coding before that. I don't think that it's going to work in current state, sorry. |
Ok thanks for confirming. |
As the error is similar, this may be helpful: #804 |
EDIT: I might just be dumb, this probably shouldn't work with Electron, right?
Getting the following issue only when running Electron.
The first issue I was getting was with the remote debugger
which I fixed by exporting
ELECTRON_EXTRA_LAUNCH_ARGS=--remote-debugging-port=9222
. I'd suggest some way to handle this internally, or at least a line of documentation.It seems like
await metamask.initialSetup({ secretWords, network, password });
from the plugin is being called before puppeteer has been been properly set up.Note that I've configured metamask to use a custom network.
The text was updated successfully, but these errors were encountered: