MetaMask / MetaMask/metamask-extension
[Bug]: Solana source tx never lands in Activity/toasts.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### Describe the bug
While testing RC 13.50.0 I noticed that when Bridging from Solana to other networks tha the toast `Transaction submitted` and `Transaction completed` won’t appear, and in the activity there is no transaction in progress. Hovewer the funds eventually arrive. Only way to fix that is to switch account back and forth or restart the Extension.
According to Cursor most likely the Solana snap (or Accounts / multichain-transactions) does not push the new tx into the currently selected account’s list. Switching account or restarting forces a refetch, the signature appears.
Here's some examples:
SOL-ETH (Robinhood)
https://github.com/user-attachments/assets/6d685903-b7f1-4d89-ba9f-d513e56b01dd
SOL-Monad
https://github.com/user-attachments/assets/ed32ff58-cb01-43f4-8c18-1989cde41d22
### Expected behavior
_No response_
### Screenshots/Recordings
_No response_
### Steps to reproduce
1. Bridge from Solana to any network
2. Notice that toast won't appear and tx is not found in the activity
### Error messages or log output
```shell
```
### Where was this bug found?
Internal release testing
### Version
13.50.0
### Build type
None
### Browser
Chrome
### Operating system
MacOS
### Hardware wallet
_No response_
### Additional context
_No response_
### Severity
_No response_
Contributor guide
Research direction
Reproduce a Solana-to-network bridge and observe the missing toast and activity entry. Start by tracing the Solana snap and the Accounts or multichain-transactions flow that should add the transaction to the selected account. Done means the submitted and completed toasts appear and the transaction is visible in Activity without switching accounts or restarting the extension.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100