status-im / status-desktop

Status Desktop client made in Nim & QML
https://status.app
Mozilla Public License 2.0
297 stars 79 forks source link

Contact's ens name is not displaying in the member list or contact card #16681

Open virginiabalducci opened 1 week ago

virginiabalducci commented 1 week ago

Bug Report

Description

When a user is in a group chat or in a community, if there is a mutual contact that has purchased an ens name, the ens name should display. If the user has a ens name, they can see their ens name attached to their profile, but if someone else also has an ens name they don't see it.

I'm not sure if the user should also see the ens name of a non-mutual member of a community or a group chat, I'd think they should see the ens name.

Steps to reproduce

  1. Log in with a user that is part of a community or a group chat that contains one member with an ens name

Expected behavior

The user should see if another user has an ens name

Actual behavior

Member list: User sees their own ens username, do not see other's ens name

The user sees another user without the ens name, the profile name displays instead of the ens name. User sleepy bird. status.eth sees their own ens name Image

Contact card: This user should see mutual contact user "Tabby Cat" 's ens name Image

seeing the member list by logging in with a different user, "sleepy cat.stateofus.eth (Tabby Cat display name)", user 'sleepybird.stateofus.eth' shows with the nickname given or profile name, instead of the ens name. Image

User "Tabby Cat" can see in the profile list their own ens name, but if this profile card is seen from a contact, the ens name does not show Image

User "Tabby Cat" does not see sleepybird.stateofus.eth ens name, only nickname displays Image

More screenshots with comparisons of different views of the same profile:

Image

Image

Additional Information

jrainville commented 1 week ago

@virginiabalducci were the ENS names just recently purchased? There is a small delay between buying them and others seeing it, because the others need to verify that the ENS is indeed bought by them.

On 2.30, I do see some people with ENS names, so it makes me think that it's indeed a "timing" issue.

virginiabalducci commented 1 week ago

@virginiabalducci were the ENS names just recently purchased? There is a small delay between buying them and others seeing it, because the others need to verify that the ENS is indeed bought by them.

On 2.30, I do see some people with ENS names, so it makes me think that it's indeed a "timing" issue.

Thanks for the quick reply! these are old accounts that already have ens purchased for like a month ago. One account 'sleepybird' has an ens name purchased in mainnet, the other user 'sleepycat' has an ens purchased in testnet, but this issue is reproducible for both

jrainville commented 1 week ago

@virginiabalducci were the ENS names just recently purchased? There is a small delay between buying them and others seeing it, because the others need to verify that the ENS is indeed bought by them. On 2.30, I do see some people with ENS names, so it makes me think that it's indeed a "timing" issue.

Thanks for the quick reply! these are old accounts that already have ens purchased for like a month ago. One account 'sleepybird' has an ens name purchased in mainnet, the other user 'sleepycat' has an ens purchased in testnet, but this issue is reproducible for both

Ok thanks for the info.

I'm pretty sure that the mainnet ENS name won't work when you,re in testnet and vice-versa for obvious reasons.

However, you should see the one that is from your own network.

Then is the account you were using to test very fresh and seeing those accounts for the first time?