903345 - [B2G][Helix][tongxiao]When change a contact "Zhabgfds" 's phone number for many times, it can not match correctly in call records.

Status: RESOLVED DUPLICATE of bug 976990

(Firefox OS Graveyard :: Gaia::Dialer, defect, P2)

Description

[lecky]

Attachment: device.png

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; Tablet PC 2.0)

Steps to reproduce:

1.save "Zhabgfds" for its phone number is 588882844
2. make a call and update its number.
3. do up repeatly.


Actual results:

1.For forth time, the number is not match to "Zhabgfds" in call records.

Ref attachment.


Expected results:

1.Everytime the number can match to "Zhabgfds" in call records.

Comment 1

[Wayne Chang [:wchang]]

Hi Alberto, can you check also from the described STR for possibilities of this occurring?

Comment 2

[bweng]

We have tried the STR for more than 10 calls but so far I am unable to repro this issue.

The build we are using is 20130904042205

Comment 3

[lecky]

I will do a second test and feedback soon.

Thanks!

Comment 4

[lecky]

I think the problem is still exist.

Please see the scrrenshot.

Thanks!

Comment 5

[lecky]

Attachment: screen shot

Comment 6

[William Hsu [:whsu]]

Hi, all,

Interesting. Now, I can use a easy way to reproduce this bug.
This bug easily happens on first time launched contact app.

* STR:
 1. Flash a new build to helix device or reset the helix device.
 2. Launch the contact app
 3. Add a contact
 4. Tap the added contact
 5. Tap the phone number to make a call
 6. Hang up
 7. Update the phone number
 8. Repeat Step5 ~ Step7 three times.
 9. Launch call log

* Test build:(Mozilla-b2g18_v1_1_0_hd-helix/2013-09-05-04-22-01)
  + Mercurial-Information
    - Gecko revision="838455b3eb13"
  + Git-information
    - Gaia revision="f0d08182afbf424b405b1d3864f557ef7c4f70c1"
  + Gecko version: 26.0a1


Attaching the screenshot.


--------- Change the status to "NEW" ---------

Comment 7

[William Hsu [:whsu]]

Attachment: Contact App - Incorrect call log

Comment 8

[lecky]

Hi William:

   Are you wished to fix this issue in HD v1.1?

Thanks!

Comment 9

[William Hsu [:whsu]]

Hi, Wayne,

Do you think we need to fix this problem on V1.1.0 branch?
Thank you.

Comment 10

[Wayne Chang [:wchang]]

Adding Francisco and Anthony.

QA can now consistently reproduce this bug, can you investigate?

Recommend not blocking as it requires the number to be changed many times. Please renom if you feel otherwise.

Comment 11

[lecky]

Hi :

   Are you wished to fix this issue in HD v1.1?

Thanks!

Comment 12

[Wayne Chang [:wchang]]

Lecky,
Please do not clear need information for other people.

William, can you kindly check this on v1.2 as well?

Comment 13

[Anthony Ricaud (:rik)]

William: Does this reproduce on something else than a Helix?

Comment 14

[Jason Smith [:jsmith]]

QA Wanted for comment 13 - let's try testing this on something other than Helix (e.g. Buri).

Comment 15

[Francisco Jordano [:arcturus] [:francisco]]

Sorry for the delay in the answer, I was on PTO.

I'm removing myself about the needinfo since this is a call log feature. Asking Fernando Jimenez if he knows more about this issue.

Thanks!
F.

Comment 16

[William Hsu [:whsu]]

Hi, all,

I can reproduce this bug on V1.2 branch.
I think other branches had the same problem and this was a legacy bug.

*Test Build:
 - Gaia:     a13c76f8d3c617ee57c302c103da04ed1a6298d1
 - Gecko:    http://hg.mozilla.org/releases/mozilla-aurora/rev/b34384409be6
 - BuildID   20130924004002
 - Version   26.0a2

Attaching the screenshot.

Comment 17

[William Hsu [:whsu]]

Attachment: Call log - Buri

Comment 18

[William Hsu [:whsu]]

--------- Remove QAwanted ---------

Comment 19

[Joe Cheng [:jcheng] (please needinfo)]

triage: not a blocker for v1.2. minus

Comment 20

[lecky]

 Hi :

   Are you wished to fix this issue in HD v1.1?

Thanks

Comment 21

[Wayne Chang [:wchang]]

No, and not for v1.2 either.

Please read previous comments (comment 19.)

(In reply to lecky from comment #20)
>  Hi :
> 
>    Are you wished to fix this issue in HD v1.1?
> 
> Thanks