1109003 - [Loop] Changing detail contact with/without MCC in Contact App, contact names are not updated properly in call log

Status: RESOLVED WONTFIX

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

Description

[Javier de Prado]

STR:
1.- DeviceA and DeviceB logged in Loop with MSISDN with NumA and NumB respectively.
2.- Register NumA without MCC in DeviceB's contact app as NumAWithoutMCC.
3.- Make a call from DeviceB's contact app to DeviceA (NumAWithoutMCC).
4.- DeviceA receives a call with MCC (+34....), and is added to DeviceA's call log.
5.- From DeviceA's call log, create new contact as NumBWithMCC
6.- Make again a call from DeviceB's contact app to DeviceA (NumAWithoutMCC), and check in  DeviceA's call log, there are two entries with NumBWithMcc name. (Ok)
7.- Modify in DeviceA, from contact app: Contact number from +34number to number (without MCC), as its name, from NumBWithMCC to NumBWithoutMCC.
8.- Open loop app in Device A and check in call log, two entries with num "+34number" (NOK: instead of Contact Name)
9.- Make again a call from DeviceB's contact app to DeviceA (NumAWithoutMCC), and check in  DeviceA's call log, there is a new entry with contact name (NumBWithoutMC).

EXPECTED RESULT: 
*.- In step 8, both call log entries should be NumBWithoutMCC instead of literal number (+34number).
*.- In step 9, all three call log entries should be NumBWithoutMCC. (see attachment)

Comment 1

[Javier de Prado]

Attachment: 2014-12-09-10-19-45.png

Comment 2

[Javier de Prado]

ENV:
v1.1, v 4212078
FireE comercial build.

Comment 3

[Maria Angeles Oteo (:oteo)]

Javier, if you kill Loop and launch it again, is the call log properly updated?

Comment 4

[Javier de Prado]

No. The call log remains the same, even killing loop app, leaving (logout) from loop, or reseting de device.

Comment 5

[Maria Angeles Oteo (:oteo)]

Thanks Javier, I've just tested it too and after killing and launching Loop again, the result is the same.

I think that this is corner case as users are not going to be removing the CC specially if they already have included the number in the Agenda with the CC before. Anyway, we will have a look to see if the fix is not very complex to include it in next release.

Comment 6

[Javier de Prado]

Tested again on ENV:
Flame
v2.0
Gecko-5f9dc54
Gaia-31d6c94
Loop master version, commit 51a04dd

Comment 7

[Cristian Rodriguez (:crdlc)]

My two cents. It is very difficult to solve this issue because we need to normalize telephone numbers in our logic (such as callLog as db). Currently, our algorithm is aware when a moz contact has been updated. At that moment, we search in our callLog all records that have the same contactId. For each one of them, we have to check if there are matching between identities for the moz contact and records which appear in the callLog. The matching is performed by means of using the "equal" operation ([phone] !== 645545454). We cannot use the "contain" operation because "[phone]" contains "4", "54" or ""[phone]" and they are not the same phone number. The only way to get a proper solution is using normalization for phone numbers. And it seems a strong and long work.

Comment 8

[Maria Angeles Oteo (:oteo)]

[Tracking Requested - why for this release]:

Comment 9

[BMO Automation]

Firefox OS is not being worked on