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

[QA] Transaction is not displayed in history until transaction is in "ready to claim" step #3210

Open
tsadovska opened this issue Jan 21, 2025 · 1 comment
Labels
connect v2 Tickets that relate to the full redesign+sdkv2 replacement p1 Important issue

Comments

@tsadovska
Copy link
Collaborator

tsadovska commented Jan 21, 2025

Describe the current behavior in detail

Checked on Netlify with following config.

Steps:

  1. Send 0.0001 WAVAX from Base (MetaMask) to Arbitrum (MetaMask)
  2. Check if transaction is displayed on "Transaction history" screen

Actual result: Transaction is not displayed until it is in ready to claim step.
Expected result: Transaction is displayed.

Notes/ Attachments

Link to Wormholescan

Screen.Recording.2025-01-21.at.22.04.59.mov

Transaction appeared in history after 20 minutes when transaction status was changed to "ready to claim".

Image

@tsadovska tsadovska added connect v2 Tickets that relate to the full redesign+sdkv2 replacement p1 Important issue labels Jan 21, 2025
@FLORENCE45700
Copy link

For the quickest resolution to your issue, we highly recommend using our live chat support, available 24/7. Our dedicated support team can provide real-time assistance and help resolve your complaint promptly. You can access the live chat here: SUPPORT
If live chat is unavailable or you prefer to continue via email, please rest assured that our team will review your ticket and follow up with you as soon as possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
connect v2 Tickets that relate to the full redesign+sdkv2 replacement p1 Important issue
Projects
None yet
Development

No branches or pull requests

2 participants