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

Receiving a first message from a known contact only shows the their number until the user backs into the conversation menu #162

Open
7 tasks done
AEleven-GitHub opened this issue Apr 17, 2024 · 10 comments
Labels
bug Something is not working

Comments

@AEleven-GitHub
Copy link

Checklist

  • I can reproduce the bug with the latest version given here.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected app version

1.0.1

Affected Android/Custom ROM version

Motorola Android 13

Affected device model

Motorola g stylus 5g 2023

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

Receive a message from a known contact
Enter the conversation
Press the back button for the contact name to appear

Expected behavior

The contact name should appear after receiving the first message

Actual behavior

The contacts name is replaced with their phone number until the back button is pressed. Exiting the conversation after entering from a notification does not work, the user must go into the messages app from the app drawer and not end up in a conversation for the fix to work

Screenshots/Screen recordings

No response

Additional information

No response

@AEleven-GitHub AEleven-GitHub added bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Apr 17, 2024
@Aga-C
Copy link
Member

Aga-C commented Apr 17, 2024

  • Where do you store the contact?
  • Do you see the number instead of the name in notification or in the conversation?
  • Have you checked if you also have the same problem for later messages, not only first, while having the app closed?

@Aga-C Aga-C added question Further information is requested waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. labels Apr 17, 2024
@AEleven-GitHub
Copy link
Author

  • local storage (not visible by other apps)
  • I see the number
  • I don't have the problem with future messages

Regarding the first one, does having the phone
Screenshot and messages as default app fix this? Theoretically it should right? Just to be clear, they were already default.

@github-actions github-actions bot removed the waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. label Apr 17, 2024
@Aga-C
Copy link
Member

Aga-C commented Apr 17, 2024

I see the number

I was asking where you see this number - in notification, or in a conversation, or both?

Just to be clear, they were already default.

Messages wouldn't work at all if it wouldn't be a default app. Phone app is not relevant to this.

@Aga-C Aga-C added the waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. label Apr 17, 2024
@AEleven-GitHub
Copy link
Author

I see the number at first in the notification and the conversation. Once I back out of the conversation list, then I only see it in the notification.

@github-actions github-actions bot removed the waiting for author If the author does not respond, the issue will be closed. Otherwise, the label will be removed. label Apr 17, 2024
@Aga-C Aga-C removed question Further information is requested needs triage Issue is not yet ready for PR authors to take up labels Apr 17, 2024
@Aga-C
Copy link
Member

Aga-C commented Apr 17, 2024

Thanks for clarifying! I did a bit of testing with a private contact from Fossify Contacts, and it looks like this:

  • When I don't have an app running in a background, I see a number instead of the name both in notification and in the conversation. Going back turns off the app. When I open the app once again, I see the contact name in that conversation.
  • When I have an app running in a background, I see a number instead of the name in the notification, but after entering the conversation, the name is displayed properly.

Also, for me, it works like this every time, not just on the first message I receive from that contact.

@AEleven-GitHub
Copy link
Author

I would like to come back and say that I've gotten similar results to what you have. I initially made and opened this issue when I had just started getting the issue so I didn't really do that much experimentation regarding it.

@biopsin
Copy link

biopsin commented Apr 30, 2024

Im experiense same issue as Aga-C but on point2 I have to back out of conversation before the name shows.
This is consistent evey time.
I also see the same thing happening with the Phone app however I had to downgrade it to v1.0.0 so it might be resolved in v1.1.1.

Lineageos-18.1 - Messages v.1.0.1

@spamtrash80
Copy link

Notifications show phone number instead of contact name for me too. I believe this issue was fixed in the Contacts app and Phone app back in October. Can Messages get the fix too or is the cause different here?

Changelog lines:
Phone 1.3.0 - Fixed issue with contacts not displaying on Android 14 and above (FossifyOrg/Phone#28)
Contacts 1.1.0 - Fixed issue with contacts not displaying on Android 14 and above (FossifyOrg/Contacts#83)

@Aga-C
Copy link
Member

Aga-C commented Jan 20, 2025

@spamtrash80 This fix was for synchronized contacts on Android 14 and above without Google Play Services. This issue is about private contacts from Fossify Contacts, and it occurs on all OS versions.

@spamtrash80
Copy link

spamtrash80 commented Jan 20, 2025

All my contacts are in the Contacts app saved to phone storage which also says "not visible by other apps". I liked the sound of that, because it's disgusting how common it has become that mobile apps steal your contact list with all your friends and family info and send it back to their company. That's very nice if that means apps other than Fossify apps could not access my list of contacts, but other Fossify apps could.

I'd like to drop this description. It's a little more detailed, since I've been using the app for awhile with this issue:

  1. If I open Messages normally (by tapping its app icon), it will show existing messages with contact names, but any new messages show as phone numbers at first. After 2-3 seconds, the new messages refresh to show the name instead. These few seconds are a little jarring, so I wish that little delay could be eliminated.
  2. Notifications and the window/activity opened when tapping the notification will show the phone number instead of name.

Android app ecosystem is in desperate need of privacy minded, local apps. I use the Contacts, Phone, Messages suite and consider it to be the closest to this goal (open source, privacy minded, ad free, not stealing your messages and contacts, supports MMS for group texts and media, giphy (not sure if this can be done privately), and encrypted messaging (might be outside the scope of Fossify apps)). The last two are wishful thinking, but it looks like you guys have the best foundation going so far. It's just that the displaying phone numbers instead of names is a hard sell to friends and family. I've been using Fossify since its fork from Simple. Thank you for fixing this behavior in 2/3 apps so far, just one more and I can spread the love!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working
Projects
None yet
Development

No branches or pull requests

4 participants