Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: When Bridging to Solana the activity incorrectly shows the tx incompleted #30801

Open
davibroc opened this issue Mar 6, 2025 · 2 comments
Labels
needs-triage Issue needs to be triaged regression-RC-12.14.0 Regression bug that was found in release candidate (RC) for release 12.14.0 Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. solana-beta type-bug Something isn't working

Comments

@davibroc
Copy link
Contributor

davibroc commented Mar 6, 2025

Describe the bug

When bridging to any network to Solana, the first transaction works correctly. However, for the second transaction, the getTxStatus API call returns a 500 internal error while it's pending. Once the transaction is complete, it returns the status COMPLETED correctly, but the UI still shows the transaction as pending. See the video for more details.

Expected behavior

No response

Screenshots/Recordings

tx.never.complete.mov

Steps to reproduce

  1. Select any network.
  2. Bridge any token to Solana.
  3. Monitor the network tab in the background worker.
  4. Notice that getTxStatus initially returns a 500 error, and once the transaction is completed, the UI does not show the transaction as completed.

Error messages or log output

Detection stage

During release testing

Version

12.14.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

@davibroc davibroc added the type-bug Something isn't working label Mar 6, 2025
@github-project-automation github-project-automation bot moved this to To be triaged in Bugs by team Mar 6, 2025
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Mar 6, 2025
@metamaskbot metamaskbot added regression-RC-12.14.0 Regression bug that was found in release candidate (RC) for release 12.14.0 needs-triage Issue needs to be triaged labels Mar 6, 2025
@davibroc davibroc added Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. solana-beta labels Mar 6, 2025
@Unik0rnMaggie
Copy link
Contributor

Reproduced for bridge from Avalanche network to Solana network:

Image

@davibroc
Copy link
Contributor Author

davibroc commented Mar 7, 2025

It also happens on the build without Solana when Bridging from Optimism

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Issue needs to be triaged regression-RC-12.14.0 Regression bug that was found in release candidate (RC) for release 12.14.0 Sev1-high High severity; partial loss of service with severe impact upon users, with no workaround. solana-beta type-bug Something isn't working
Projects
Status: To be fixed
Status: To be triaged
Development

No branches or pull requests

3 participants