Closed Bug 822009 Opened 12 years ago Closed 12 years ago

[SMS] Conversations on the SMS app show the phone numbers instead of the contact's name (this happens when there is no last name)

Categories

(Firefox OS Graveyard :: Gaia::SMS, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 821298

People

(Reporter: armenzg, Assigned: julienw)

References

Details

(Keywords: b2g-testdriver, unagi)

I'm in a conversation with someone on the SMS app. At the top of my conversation it shows the phone number (e.g. +19998887777) rather than the name of the contact. The contact exists with that exact phone number in my phone book. * Why shouldn't it show up their name at the top of the conversation? On the other hand, if I tap on the phone number I get suggested to create a new contact even though there is an existing contact that has that exact number. * I would expect to go to the existing contact. I'm using the 12-12 beta channel update. I'm not sure if this happened on previous updates. There is a similar issue described in bug 805205.
Wonderful! I found out that if the last name on a contact is missing the SMS app won't be able to match it! :)
Summary: [SMS] Conversations on the SMS app show the phone numbers instead of the contact's name → [SMS] Conversations on the SMS app show the phone numbers instead of the contact's name (this happens when there is no last name)
I've found that the caller ID does not work either if the last name is not specified for a contact (bug 821298). Merge both bugs if needed.
Component: Gaia → Gaia::SMS
Whiteboard: DUPEME
Depends on: 821298
For me should be a duplicate of 821298, due to the code requesting the 'Contact' is the same (so the bug is the same).
Assignee: nobody → felash
Agreed, this looks like the same bug. (even if I can't reproduce this)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
blocking-basecamp: ? → ---
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.