972103 - [B2G][FDN][Add Number]PIN2 is not accepted properly when attempting to add new number to FDN Authorized Number list.

Status: RESOLVED WONTFIX

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

Description

[Ross Kuhlman ([e-mail])]

Attachment: AddFDN_CorrectPIN.txt

When Fixed Dialing Numbers is enabled, the device can only call phone numbers that are added to the Authorized Number list. In FxOS 1.2, the user is unable to add numbers to the Authorized Number list. After entering contact details, the device prompts the user to enter a PIN2 number. Entering the correct PIN2 does nothing. The 'Done' button flashes when tapped, but otherwise does nothing.

Entering the wrong PIN does not alert the user than an incorrect PIN2 has been entered.  The user is taken back to the list of Authorized Numbers, and the contact info entered by the user is erased.

Repro Steps:
1) Updated Buri to BuildID: 20140210004002
2) Launch 'Settings' >> 'Call Settings' >> 'Fixed Dialing Numbers'
3) Tap the '+' button in the upper right corner.
4) Enter a name and valid phone number, then press 'OK'.
5) Enter a valid SIM PIN2 when prompted, and press 'Done'.

Actual:
Nothing happens.

Expected:
SIM PIN2 is accepted, and name/phone number combo is added to Authorized Numbers list.

Environmental Variables:
Device: Buri v1.2 COM RIL
BuildID: 20140210004002
Gaia: 539a25e1887b902b8b25038c547048e691bd97f6
Gecko: 2673f348598c
Version: 26.0
RIL Version: 01.02.00.019.102
Firmware Version: v1.2-device.cfg

Notes:
This issue does NOT occur in 1.3, and FDN does not exist in 1.1.

Repro frequency: 100%
See attached: logcat

Comment 1

[Ross Kuhlman ([e-mail])]

Attachment: AddFDN_IncorrectPIN.txt

Comment 2

[Ross Kuhlman ([e-mail])]

This issue also occurs in the v1.2 builds from 2014/01/13, and 2013/12/13. The fact this issue repros on a two month old build leads me to believe that this issue may be caused by the latest base image. (v1.2-device.cfg)

Comment 3

[Jason Smith [:jsmith]]

Enpei - We are seeing a lot of bustage with FDN right now (see this bug, bug 967159, and bug 968550). Could the base image play a factor into causing these problems? What do you think?

Comment 4

[Jason Smith [:jsmith]]

Didn't realize initially that this was for 1.2, not 1.3. We're no longer supporting 1.2 at this time, so this is a WONTFIX.

Comment 5

[Enpei]

(In reply to Jason Smith [:jsmith] from comment #4)
> Didn't realize initially that this was for 1.2, not 1.3. We're no longer
> supporting 1.2 at this time, so this is a WONTFIX.
Hi Jason,

Since I've done some tests as well, here is info for your reference.

For bug 967159 and 968550, I can also reproduce them on Fugu, so I don't think they has anything to do with buri v1.2-device.cfg base image.

As for this bug on v1.2, it's not totally nothing happen after enter correct PIN 2. You can press back key after enter PIN 2 and press Done, you will see the new allowed contact is added. This is still a bug. But once I change base image to 1125.cfg, it gets worse. No contact can be added in FDN totally even press back key. So I guess this bug might be related to base image for sure.