MetaMask / MetaMask/metamask-extension
[Bug]: polling starts too soon after bridging
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### Describe the bug
When bridging I noticed that the updateStatus call returns the following as seen in the video. It could be that we start polling too soon
{
“statusCode”: 409,
“message”: “Transaction not yet indexed on chain; please retry in a few seconds (chain: 1, tx: 0x92383186b855926d073a7e2fca2bf21e938484a944d4bb7a22bd0a5b2e1dafb0)“,
“type”: “TRANSACTION_NOT_INDEXED”
}
https://github.com/user-attachments/assets/417b7795-9b25-49be-9b5c-2fe81f320a3c
### Expected behavior
_No response_
### Screenshots/Recordings
_No response_
### Steps to reproduce
1. Bridge ETH to SOL
2. Notice in the network that updateStatus returns an error
### 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
Start from the updateStatus call in the bridge flow and reproduce the ETH-to-SOL transfer described in the issue using Chrome. Trace when polling begins relative to bridging, then verify that the flow no longer immediately returns TRANSACTION_NOT_INDEXED (409) because polling starts before the transaction is indexed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100