[Settings] User sees the message 'incorrect sim pin' when trying to initially enable a sim

RESOLVED INVALID

Status

Firefox OS
Gaia::Settings
RESOLVED INVALID
3 years ago
3 years ago

People

(Reporter: rpribble, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(blocking-b2g:-, b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)

Details

(Whiteboard: [2.1-Daily-Testing], URL)

Attachments

(1 attachment)

Comment hidden (empty)
(Reporter)

Comment 1

3 years ago
Description:
After flashing to a new build and opening Sim Security for the first time to initially enable a sim pin, the user may see the message 'incorrect sim pin' in error.
Sim pin security has also been seen to show a sim pin already enabled after a new flash, but no sim pin is asked of the user when unlocking the device.

Repro Steps:
1) Update a Flame device to BuildID: 
2) Navigate through ftu
3) Settings > Sim manager > Sims security > Tap SIM 1 PIN toggle
4) If the sim pin enables correctly, disable it and enable it again with a different number
  
Actual:
The user may see the messge 'incorrect sim pin' after entering a new sim pin to initially enable one.

Expected: 
User does not see this message when no sim pin has been enabled and the toggle is in the left and unhighlighted off position.
  
Environmental Variables:
Device: Flame 2.1 (319MB)
BuildID: 20140915000203
Gaia: 944e5b4582c4efa1b67cd33245dbb8f6aa25d09f
Gecko: 7546fedad918
Version: 34.0a2 (2.1)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
  
Notes:
  
Repro frequency: 70%
See attached: Video

-----------------------------------------------
This issue also occurs on the 9/15/14 v2.0 Flame and the 9/12/14 v2.1 Flame.

Device: Flame 2.0 (319MB)
BuildID: 20140915000202
Gaia: 7edd3b0b9f65c3dde235c732d270e43e055a1254
Gecko: 13e04ab68621
Version: 32.0 (2.0)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Device: Flame 2.1 (319MB)
BuildID: 20140912000203
Gaia: 7fe8807b384e1867fa4322f49a1310126fc5a849
Gecko: 1d4b0fc511dc
Version: 34.0a2 (2.1)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Creating a sim pin can result in seeing the message 'incorrect sim pin'.
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0: --- → affected
status-b2g-v2.1: --- → affected
status-b2g-v2.2: affected → ---
Flags: needinfo?(pbylenga)
Whiteboard: [2.1-Daily-Testing → [2.1-Daily-Testing]
(Reporter)

Comment 2

3 years ago
Created attachment 8489480 [details]
Logcat.txt
QAWanted for branch checks.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Keywords: qawanted
The bug repros on KK Flame 2.2, Flame 2.1 and Flame 2.0
Actual result: Attempting to establish a SIM PIN will not work unless the previous SIM PIN is used.

Flame 2.2
BuildID: 20140915201445
Gaia: e2d70bee03b5380ac327a145e5d694fb2443f018
Gecko: 0e581e529fd6
Platform Version: 35.0a1
Firmware Version: v165
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Flame 2.1
BuildID: 20140916091859
Gaia: 47939f4c41d0c941e5047e5d1af74a79b7d8e0d5
Gecko: 5b4236189b9b
Platform Version: 34.0a2
Firmware Version: v165
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Flame 2.0
BuildID: 20140916091857
Gaia: 95314e27da38b8c4edf965a77eded16cc5729ea8
Gecko: 5ecb32d79d03
Platform Version: 32.0
Firmware Version: v165
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.2: --- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted
[Blocking Requested - why for this release]: confusing and misleading error messages leads to bad UX
blocking-b2g: --- → 2.0?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
We need a branch check here on 1.4.
QA Whiteboard: [QAnalyst-Triage+]
Keywords: qawanted
QA Contact: ckreinbring
The bug does repro on JB Flame 1.4
Actual result: Attempting to establish a SIM PIN will not work unless the previous SIM PIN is used.

BuildID: 20140917073803
Gaia: efa2b8cb095407df942fee7732a5547c7034ef9b
Gecko: a7f7eaf3f682
Platform Version: 30.0
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v1.4: --- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
The triage group had some difficulty understanding the STR here.  We were specifically confused about the necessity of a pre-existing SIM PIN.  Can you clarify, please, Rachel?  Thank you.
Flags: needinfo?(rpribble)
I reproduced this issue as well, looks like if you've ever setup a sim pin and the past and disabled THAT PIN all further setup attempts with different PINs give an error.

Clarified str's:

1. Setup a sim pin 1111
2. disable the sim pin
3. enable the sim pin with 2222

Expected: Sim PIN enabled screen is shown
Actual: Sim PIN confirmation failure screen is shown
Flags: needinfo?(rpribble)
It looks like the tester expects to be able to use a new SIM PIN every time they enable it. This is not how SIM PIN works.

This not a bug.

If you wish to change the SIM PIN you need to do it via "Change SIM PIN"
Status: NEW → RESOLVED
blocking-b2g: 2.0? → -
Last Resolved: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.