MetaMask / MetaMask/metamask-extension

[Bug]: Snaps - `npm:@metamask/snap-simple-keyring-snap was stopped and the request was cancelled. This is likely because the Snap crashed.`

Open
#44,026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Sev2-normal team-core-platform type-bug
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

### Describe the bug

There is an intermittent failure in our e2e which shows an issue in the wallet side: after installing a snap simple keyring and proceed with the next action, we get the error `npm:@metamask/snap-simple-keyring-snap was stopped and the request was cancelled. This is likely because the Snap crashed.`

Tests we've seen so far, in which the issue arises intermittently:
- Snap Account Contract interaction deposits to piggybank contract
- Create and remove Snap Account create snap account and remove it by removing snap
- Create Snap Account creates multiple Snap accounts with increasing numeric suffixes

### Expected behavior

no crash

### Screenshots/Recordings

Image

### Steps to reproduce

Check logs in the failed test runs. The issue can be surfaced when we install the snap simple keyring and then perform action (but it's not happening always)

See:
- https://github.com/MetaMask/metamask-extension/actions/runs/28359723203/job/84013331595
- https://github.com/MetaMask/metamask-extension/actions/runs/28352017324/job/83988126371
- https://github.com/MetaMask/metamask-extension/actions/runs/28381261957/job/84086908062

### Error messages or log output

```shell

```

### Where was this bug found?

Internal release testing

### Version

main

### Build type

None

### Browser

Chrome

### Operating system

Linux

### Hardware wallet

_No response_

### Additional context

_No response_

### Severity

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the logs from the three linked GitHub Actions runs and the e2e tests covering Snap Account Contract interaction deposits, Snap Account creation and removal, and multiple Snap accounts. Reproduce the sequence of installing the simple keyring snap and performing the next action. Done means the snap no longer crashes and the affected e2e tests pass reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.