Skip to content
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.

How avoid import seed to metamask every time #120

Closed
xflag opened this issue Jul 28, 2022 · 4 comments · Fixed by #238
Closed

How avoid import seed to metamask every time #120

xflag opened this issue Jul 28, 2022 · 4 comments · Fixed by #238
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed P0 Critical. Tacked by core team

Comments

@xflag
Copy link

xflag commented Jul 28, 2022

When I bootstrap dappeteer,it need import seed,add network,switch network,it seems too slow.Futhermore,it failed sometimes when add new network to metamask.Are there any way to launch by my own prepared metamask to avoid these duplicate steps?

@xflag xflag added the help wanted Extra attention is needed label Jul 28, 2022
@ccforeverd
Copy link

  const browser = await dappeteer.launch(puppeteer, {
    // metamaskVersion: 'v10.15.0',
    metamaskPath: join(__dirname, '../metamask/v10_15_0'),
    // args: ['--lang=en-US,en', '--proxy-server=127.0.0.1:7890'],
    args: ['--lang=en-US,en'],
    devtools: true
  })

@mpetrunic
Copy link
Member

We could try adding an option to cache browser data after metamask is set-up. This needs more research.

@mpetrunic
Copy link
Member

@BeroBurny @danforbes This would be useful to speed up snap testing and to insure a clean state for every test but it's out of scope for M1

@mpetrunic mpetrunic added P0 Critical. Tacked by core team enhancement New feature or request and removed feature labels Nov 11, 2022
@mpetrunic
Copy link
Member

There are multiple options how to achieve this:

  • start using persisted context (we already do that for playwright)
  • use rdp API to import context (how metamask does it)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request help wanted Extra attention is needed P0 Critical. Tacked by core team
Projects
Status: Done/Closed
Development

Successfully merging a pull request may close this issue.

4 participants