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]: For imported accounts, tokens are not immediately recognized until there is a network switch or the extension is reloaded #25156

Open
sleepytanya opened this issue Jun 7, 2024 · 1 comment
Labels
regression-develop Regression bug that was found on development branch, but not yet present in production send-swap Sev3-low Low severity; minimal to no impact upon users stale issues and PRs marked as stale team-assets type-bug

Comments

@sleepytanya
Copy link
Contributor

Describe the bug

For imported accounts, tokens are not immediately recognized until there is a network switch or the extension is reloaded.

Expected behavior

Token assets detected and imported.

Screenshots/Recordings

Video:
https://jam.dev/c/413213f8-3e3a-412a-acdb-f53607333649

Steps to reproduce

  1. Import account which has different tokens
  2. Notice that tokens are not autodetected
  3. Try switch a network or reload extension

Error messages or log output

No response

Version

develop

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

@sleepytanya sleepytanya added type-bug regression-develop Regression bug that was found on development branch, but not yet present in production labels Jun 7, 2024
@gauthierpetetin gauthierpetetin added team-assets Sev3-low Low severity; minimal to no impact upon users labels Jun 10, 2024
Copy link
Contributor

github-actions bot commented Sep 8, 2024

This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 45 days if there is no further activity. The MetaMask team intends on reviewing this issue before close, and removing the stale label if it is still a bug. We welcome new comments on this issue. We do not intend on closing issues if they report bugs that are still reproducible. Thank you for your contributions.

@github-actions github-actions bot added the stale issues and PRs marked as stale label Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression-develop Regression bug that was found on development branch, but not yet present in production send-swap Sev3-low Low severity; minimal to no impact upon users stale issues and PRs marked as stale team-assets type-bug
Projects
Status: To be fixed
Status: To be fixed
Development

No branches or pull requests

2 participants