1075726 - Calling voicemail by long-pressing the 1 button (and then hanging up) leaves the dialer with "123" pre-entered (and possibly with a contact preselected for autodialing)

Status: RESOLVED WONTFIX

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

Description

[Daniel Holbert [:dholbert]]

STR:
 0. Optional: type some numbers into the dialer
 1. Long-press "1"
    --> call begins with voicemail
 2. Hang up the voicemail call.
  (if this leaves you with an error screen [bug 1075699], dismiss the error]

 3. Inspect the contents of the dialer's text field

EXPECTED RESULTS: The text field should be as I left it. (empty, or perhaps containing whatever numbers I'd dialed in step 0)

ACTUAL RESULTS: The dialer has "123" pre-entered in its textfield. (Moreover, I happen to have a contact who has "123" in the middle of their phone number, so the dialer has them pre-entered to be called with the touch of a button. If I accidentally tap on that part of the dialer, I'll unwittingly call them.)

Comment 1

[Daniel Holbert [:dholbert]]

Attachment: screenshot of what I see after hanging up on voicemail

Comment 2

[Daniel Holbert [:dholbert]]

I'm using a Flame with an up-to-date FxOS 2.1 aurora-channel build, BTW.

Comment 3

[Johan Lorenzo [:jlorenzo]]

I'm not able to reproduce with my French SIM Card, can you Doug?

Comment 4

[Daniel Holbert [:dholbert]]

(FWIW: I have a single SIM card in my phone, for T-Mobile (US).)

Comment 5

[Doug Sherk (:drs) (inactive)]

I'm also unable to repro this on either 2.2/master or 2.1, and with either 1 SIM or 2. I tried adding some contacts with '123' as part of their phone number, and there was no difference.

Daniel, can you think of anything different about your setup?

Comment 6

[Daniel Holbert [:dholbert]]

Unsurprisingly, "123" appears to be the phone number for voicemail on T-Mobile, per http://support.t-mobile.com/docs/DOC-8024 .  So, maybe this is happening for me and not for you because I'm on T-Mobile, and your carrier might use a different technique for connecting to voicemail.

Also, rik says in IRC that "when you have an error, we put the number dialed in the view" -- hence, this might only be happening as a result of bug 1075699.

Comment 7

[Daniel Holbert [:dholbert]]

dbaron can reproduce this in his 2.2 build, too. (I just had lunch with him & he tried it while sitting next to me & reproduced it.)

(His carrier is T-Mobile, as well.)

Comment 8

[Doug Sherk (:drs) (inactive)]

Tamara, could you try to repro this?

Comment 9

[Tamara Hills [:thills]]

Just like above, I'm able to repro on 2.1 and 2.2 for my T-Mobile phone (but not on 2.0).  It doesn't have anything to do with the long press, but rather the digits 123.  I'm trying to debug into Gecko to see where we are tripping up.

Comment 10

[Johan Lorenzo [:jlorenzo]]

Adding QA wanted to check the 2.0 branch (only) with a T-Mobile SIM card.

Comment 11

[Adam Alldredge [:AdamA][Inactive]]

This issue is occurring on 2.0 Flame.

Device: Flame 2.0 (Shallow Flash)
BuildID: 20141006044157
Gaia: 26670a3193b57ead978ef2faefc2a679ea57f8d4
Gecko: c06b369ccda7
Version: 32.0 (2.0)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Result:
123 appears in the dialer after calling and cancelling voicemail.
-------------------------------------------------------------------
This issue does not occur in 2.0 Flame (Base)

Device: Flame 2.0 (Base)
BuildID: 20140904160718
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Result:
123 is not entered in dialer after calling and cancelling voicemail.

Comment 12

[Daniel Holbert [:dholbert]]

(In reply to Daniel Holbert [:dholbert] from comment #6)
> Also, rik says in IRC that "when you have an error, we put the number dialed
> in the view" -- hence, this might only be happening as a result of bug 1075699.

This theory about this bug's cause turned out to be incorrect -- bug 1075699 is now fixed (which I've locally verified), but I can still reproduce this bug here.

I'm using my Flame on Aurora channel, FxOS 2.1.

Comment 13

[Anthony Ricaud (:rik)]

Nope, my theory still applies :)

When we place a call [1], we pass an error handler that displays the number back [2]. With bug 1075699 applied, we don't display the error but we still call the error handler [3].

[1] https://github.com/mozilla-b2g/gaia/blob/b2f6a1aced1e3a81f90af4b48f4b417a5d5b08e9/apps/communications/dialer/js/dialer.js#L466
[2] https://github.com/mozilla-b2g/gaia/blob/b2f6a1aced1e3a81f90af4b48f4b417a5d5b08e9/apps/communications/dialer/js/dialer.js#L456
[3] https://github.com/mozilla-b2g/gaia/blob/b2f6a1aced1e3a81f90af4b48f4b417a5d5b08e9/apps/communications/dialer/js/telephony_helper.js

Comment 14

[Daniel Holbert [:dholbert]]

(Unsurprisingly, I'm still seeing this bug on up-to-date Firefox OS 3.0, on a Sony Xperia Z3.)

Comment 16

[BMO Automation]

Firefox OS is not being worked on