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]: Incorrect token in Receive notification: You received xxx ETH on Polygon network #7669

Open
seaona opened this issue Nov 2, 2023 · 6 comments
Labels
Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking stale Issues that have not had activity in the last 90 days team-assets type-bug Something isn't working

Comments

@seaona
Copy link
Contributor

seaona commented Nov 2, 2023

Describe the bug

Problem: whenever I receive some MATIC on Polygon testnetwork, I see the notification saying You received xxx ETH instead of MATIC.

Expected behavior

The token in the Receive notification should be correct, according to the network I have selected

Screenshots/Recordings

Screenshot from 2023-11-02 09-55-21

Screenshot from 2023-11-02 09-59-14

Steps to reproduce

  1. Add Polygon Mumbai network https://chainlist.org/?testnets=true&search=mumbai
  2. Claim some MATIC tokens on the faucet https://faucet.quicknode.com/polygon/mumbai/?transactionHash=0xa65ef3490c395247c5c9ec52d236144dd911c087afbed5fcb367603a7269780c
  3. See notification appear in the wallet, saying you received xxx ETH, instead of MATIC

Error messages or log output

No response

Version

7.9.0 production

Build type

None

Device

Pixel 6

Operating system

Android

Additional context

No response

Severity

No response

@seaona seaona added type-bug Something isn't working Sev3-low A possible confusion or deception that is only hypothetical & has no known instances in the wild labels Nov 2, 2023
Copy link
Contributor

github-actions bot commented Feb 4, 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 7 days. Thank you for your contributions.

@github-actions github-actions bot added the stale Issues that have not had activity in the last 90 days label Feb 4, 2024
Copy link
Contributor

This issue was closed because there has been no follow activity in 7 days. If you feel this was closed in error please provide evidence on the current production app in a new issue or comment in the existing issue to a maintainer. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2024
@seaona seaona removed the stale Issues that have not had activity in the last 90 days label Mar 19, 2024
@seaona
Copy link
Contributor Author

seaona commented Mar 19, 2024

this shouldn't be closed as it's still present in prod

@NicolasMassart
Copy link
Contributor

Given Mumbai network is deprecated and soon to be removed from MM, @seaona could you update the test instructions please?

@gauthierpetetin
Copy link
Contributor

Draft PR #8699 needs decision on asset symbol and source to use

@hesterbruikman hesterbruikman added Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking and removed Sev3-low A possible confusion or deception that is only hypothetical & has no known instances in the wild labels Apr 18, 2024
Copy link
Contributor

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 7 days. Thank you for your contributions.

@github-actions github-actions bot added the stale Issues that have not had activity in the last 90 days label Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking stale Issues that have not had activity in the last 90 days team-assets type-bug Something isn't working
Projects
Status: To be fixed
Status: To be fixed
Development

No branches or pull requests

5 participants