MetaMask / MetaMask/metamask-extension

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

Open
#37,473 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-snaps regression-main 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

This error appears in the console during the `reset-wallet.spec` [GitHub CI](https://github.com/MetaMask/metamask-extension/actions/runs/19028411104/job/54337611458?pr=36223#step:12:4528) and [`forgot-password.spec`](https://github.com/MetaMask/metamask-extension/actions/runs/19041147518/job/54379891273?pr=36223#step:12:4871), when `this.snapController.clearState()` is called before creating new vault.

Couldn't reproduce the error in the local CI as well as in manual testing.

Image

### Expected behavior

_No response_

### Screenshots/Recordings

_No response_

### Steps to reproduce

Please refer to this CIs,
https://github.com/MetaMask/metamask-extension/actions/runs/19028411104/job/54337611458?pr=36223#step:12:4528
https://github.com/MetaMask/metamask-extension/actions/runs/19041147518/job/54379891273?pr=36223#step:12:4871

### Error messages or log output

```shell
Error: npm:@metamask/message-signing-snap was stopped and the request was cancelled. This is likely because the Snap crashed.
```

### Detection stage

On main branch

### Version

main

### Build type

None

### Browser

Chrome

### Operating system

MacOS

### 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 with the reset-wallet.spec and forgot-password.spec failures in the linked GitHub Actions runs, focusing on the this.snapController.clearState() call before a new vault is created. Compare the CI logs with local and manual runs, then identify a reliable reproduction and verify that both cited tests complete without the message-signing Snap cancellation.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.