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] Wrong Account name displayed on the first Dapp interaction #6272

Closed
seaona opened this issue Apr 26, 2023 · 3 comments
Closed

[Bug] Wrong Account name displayed on the first Dapp interaction #6272

seaona opened this issue Apr 26, 2023 · 3 comments
Assignees
Labels
Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking team-confirmations-secure-ux DEPRECATED: please use "team-confirmations" label instead type-bug Something isn't working

Comments

@seaona
Copy link
Contributor

seaona commented Apr 26, 2023

Describe the bug
Whenever I perform a dapp interaction for the first time, I can see how the To field displays the correct address of the contract, but we also see an account name, i.e. Account 2 which is not correct, nor corresponding to the address.

This seems to happen only the first time I start a dapp interaction with a new wallet. If I try again, the Account name is removed and I see only the correct address (expected).
Maybe there are more ways to repro this behaviour.

Screenshots

mobile-acct-name-wrong.webm

To Reproduce
Steps to reproduce the behavior

  1. Build MM for the first time
  2. Go to test dapp
  3. Click Send tx (i.e. legacy
  4. See recipient displays both an address an Address 2 which are not matching

Expected behavior
Address 2 should not be displayed as it's not the same address as the recipient.

Smartphone (please complete the following information):

  • Device: Pixel 6
  • OS: android
  • App Version: 6.5.0

to be added after bug submission by internal support / PM
Severity

  • How critical is the impact of this bug on a user?
  • Add stats if available on % of customers impacted
  • Is this visible to all users?
  • Is this tech debt?
@seaona seaona added type-bug Something isn't working team-confirmations-secure-ux DEPRECATED: please use "team-confirmations" label instead labels Apr 26, 2023
@bschorchit bschorchit added the Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking label Apr 27, 2023
@segun
Copy link
Contributor

segun commented May 10, 2023

This could be related to 6331

@blackdevelopa
Copy link
Contributor

blackdevelopa commented May 17, 2023

Hi @seaona, this seems to be related to 6131. I tested the fix we have for it and this issue is also handled. http://recordit.co/mqqZ2yRsZp

cc @segun

@bschorchit
Copy link

Closing as #6446 was merged

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 team-confirmations-secure-ux DEPRECATED: please use "team-confirmations" label instead type-bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants