Closed Bug 982773 Opened 11 years ago Closed 9 years ago

[B2G][SMS] Contacts imported from Facebook do not appear in manual search to be added to an sms

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v1.3 affected, b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected)

RESOLVED WORKSFORME
tracking-b2g backlog
Tracking Status
b2g-v1.3 --- affected
b2g-v1.4 --- affected
b2g-v2.0 --- affected
b2g-v2.1 --- affected

People

(Reporter: rpribble, Unassigned)

References

Details

(Whiteboard: [priority], permafail )

Attachments

(2 files)

Description: Contacts the have been imported from Facebook do not show up in the suggestion list when manually entering a contacts name in the 'to' field, regardless of whether or not they have a valid phone number listed. Repro Steps: Prerequisite: Have contacts imported from multiple sources with valid phone numbers attached to their accounts, including Facebook. 1) Updated buri to BuildID: 20140312040203 2) Tap sms icon 3) Create a new message 4) Begin typing the name of a Facebook-imported contact (with a valid phone number) in the 'to'bar 5) Observe Facebook contact fail to appear in list of suggestions Actual: Facebook contacts (with or without valid phone numbers) do not appear in the suggestion list when manually typing a contact's name. Expected: All contacts able to receive the sms appear in suggestion list. Environmental Variables: Device: buri v1.4 MOZ ril BuildID: 20140312040203 Gaia: 3005269d4dcabcc7d27eaf72bda44a969873af8c Gecko: 23005b395ae8 Version: 30.0a1 Firmware Version: v1.2-device.cfg Notes: Repro frequency: 100%
Attached image MultipleMContacts.png
Attached image OnlyOneMSuggestion.png
Yep, I think this has not been implemented yet. Not sure there is another bug though, so thanks for opening this one.
Whiteboard: dogfood1.4
Whiteboard: dogfood1.4 → dogfood1.4, burirun1.4-2
As Julien pointed out in comment 3 something pending to be implemented, nominating to v1.5? to be discussed during triage meeting. Thanks! Notice that the issue is also occurring when typing the phone number of a Facebook-imported contact in the 'to' bar (so we'd say in step #4: Begin typing the name (FB contact with a valid phone number) or phone number of a Facebook-imported contact in the 'to'bar)
blocking-b2g: --- → 1.5?
triage: add to targeted list
blocking-b2g: 1.5? → backlog
Whiteboard: dogfood1.4, burirun1.4-2 → dogfood1.4, burirun1.4-2[priority]
Whiteboard: dogfood1.4, burirun1.4-2[priority] → [priority], permafail
AFAIK, we didn't perform any integration with the Facebook datastore.
Yes we did, but not here; I think it works when receiving a SMS or to display threads or the inbox.
(In reply to Julien Wajsberg [:julienw] from comment #7) > Yes we did, but not here; I think it works when receiving a SMS or to > display threads or the inbox. Sorry, my bad with the explanation, I was talking about the integration in the contact search.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(dharris)
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(dharris)
blocking-b2g: backlog → ---
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: