Closed
Bug 821039
Opened 13 years ago
Closed 8 years ago
[Gaia][Contacts] Calling or sending SMS to a contact imported from Facebook - the contact's name does not appear in the history
Categories
(Firefox OS Graveyard :: Gaia::Contacts, defect, P2)
Tracking
(blocking-basecamp:-, b2g-v2.2 affected)
| Tracking | Status | |
|---|---|---|
| b2g-v2.2 | --- | affected |
People
(Reporter: rdaub, Unassigned)
Details
(Keywords: b2g-testdriver, unagi, Whiteboard: [sms-most-wanted])
STEPS TO REPLICATE:
1. From a freshly flashed phone, import contacts from Facebook.
2. Send an SMS or call one of the contacts that has a phone number listed.
3. Go to the SMS or call history - the phone number is listed, but not the contact's name imported from Facebook.
WORKAROUND:
1. From the SMS or call history, choose to add that phone number to your contacts.
2. Select the newly created contact.
3. Select "Link Contact"
4. Link the contact to the existing, corresponding Facebook contact.
5. Now SMS and call history will correctly display that contact's name.
Please feel free to contact me directly if a screenshot or video would assist in replicating the issue.
Thanks!!
Comment 1•13 years ago
|
||
For calling and call log bug 816563 has solved that, please use master to test it.
For SMS there is no way to fix that as the FB Cache is only available in the Comms App.
Comment 2•13 years ago
|
||
Triage: BB+, P2 - severe usability issue, C3
blocking-basecamp: ? → +
Keywords: verifyme
Priority: -- → P2
Target Milestone: --- → B2G C3 (12dec-1jan)
Comment 3•13 years ago
|
||
This is a known issue of the Facebook licence limitation. I won't block on this because the fix require an horrible hack - moving the sms app in the code of the communications app.
blocking-basecamp: + → ?
| Reporter | ||
Comment 5•13 years ago
|
||
I verified that for *calling and call logs* this issue has been resolved, as reported by Jose.
Vivien: That is understandable. "Horrible hacks are horrible," and I recognize that there are many pressing issues to focus for V1.
However, I believe this is something that should be looked into in the future.
From a user's perspective it might be very confusing why call logs show the correct contact information, but not SMS logs.
Thanks for the explanations and for listening!
(In reply to Ralph Daub [:rdaub] from comment #5)
> I verified that for *calling and call logs* this issue has been resolved, as
> reported by Jose.
>
> Vivien: That is understandable. "Horrible hacks are horrible," and I
> recognize that there are many pressing issues to focus for V1.
>
> However, I believe this is something that should be looked into in the
> future.
>
> From a user's perspective it might be very confusing why call logs show the
> correct contact information, but not SMS logs.
>
> Thanks for the explanations and for listening!
Hello Ralph! Is it ok if the verifyme tag is removed, or is there something that still should be verified? Thanks!
Comment 7•11 years ago
|
||
Julien, we reviewed this bug on contacts triage and it seems that SMS already added support for FB contacts. Can you verify that this issue is not happening anymore, please? Thanks!
Flags: needinfo?(felash)
Comment 8•11 years ago
|
||
I think it's working although I'm not sure all cases are working.
QA, can you please do some thorough tests using unlinked facebook contacts (means: contacts that you imported from Facebook but were not previously existing in your contact list) in the SMS app?
Flags: needinfo?(felash)
Keywords: qawanted
Comment 9•11 years ago
|
||
I can verify that I got this issue to occur on Flame 2.2 KK. I imported a facebook contact with an empty contacts list. I made the call and the recipient info was there but then looking at the call log it shows the number and Unknown.
As far as SMS, if I type the number in manually then I see the number and unknown contact beneath it even though the number is for a known contact.
Let me know if you want a branch check on this.
Environmental Variables:
Device: Flame 2.2 KK
BuildID: 20141217035735
Gaia: d22dfece04fc00457e8369c660c11f945b088d2f
Gecko: cb8ad2251c09
Version: 37.0a1 (2.2)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.2:
--- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted
Comment 10•11 years ago
|
||
UPDATE: I create a conversation with the known FB contact so it has the correct name in the list of threads (example: RolandQA). Then I back out and start a brand new sms thread and manually type the phone number of the contact so that it says unknown. When I send this message, I find that the message combines with the old thread and renames the known contact back to Unknown.
Comment 11•11 years ago
|
||
Whoops forgot to finish that last comment.
Is this a new bug in comment 10 or just more fallout from this bug? Let me know what you think.
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Comment 12•11 years ago
|
||
Yeah, it's more a fallout of this bug;
So as I expected, we didn't cover all use cases, sadly.
Updated•11 years ago
|
Whiteboard: [sms-most-wanted]
Comment 13•11 years ago
|
||
Thanks for all the testing !
Comment 14•8 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•