Closed
Bug 1118423
Opened 10 years ago
Closed 7 years ago
[Dialer][SIM PIN] - When PUK-locking your SIM card and correctly resetting the SIM PIN user is presented with an misleading / incorrect error message of "Your SIM card is PUK-locked"
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Tracking
(b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)
People
(Reporter: jmitchell, Unassigned)
References
Details
(Whiteboard: [2.2-Daily-Testing])
Attachments
(2 files)
Description:
When you incorrectly enter the SIM PIN 3 times you are taken to an "Enter PUK code" page where you must enter the PUK code and create a new PIN. This can be encountered from a number of different locations where you might be required to enter your SIM PIN (After lockscreen on Reboot, Settings > Sim Manager, etc. When you incorrectly enter your SIM PIN 3 times when trying to change it via the dialer app you encounter a misleading / incorrect error message after the "Enter PUK code" page.
Repro Prerequisite: Have SIM PIN enabled under Settings > SIM Manager > SIM Security
Repro Steps:
1) Update a Flame to 20150106010234
2) Start Dialer App
3) send **04*1234*6789*6789# (would change your PIN code from "1234" to "6789", update 1234 or 6789 as needed for your SIM but use INCORRECT SIM PIN)
4) Repeat UNTIL PUK Reset screen is encountered
5) Enter your SIM PUK code and create a new PIN
Actual:
After resetting the PIN an error message is encountered "Your SIM card is PUK-locked"
Expected:
This error might be encountered BEFORE resetting the SIM PIN but not after successfully resetting the PIN.
Environmental Variables:
Device: Flame Master (2.2 KK, Nightly, Full-flashed)
Build ID: 20150106010234
Gaia: b77e0d56d197e0ee02d801a25c784130d888c9db
Gecko: 2a193b7f395c
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 37.0a1 (Master)
Firmware Version: V18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Repro frequency: 5/5
Link to relevant test case: https://moztrap.mozilla.org/manage/case/14361/
See attached: logcat, screenshot
-----------------------------------------------------------------------
This issue DOES occur on 2.1, 2.0, 1.4 (v165 base-only) 2.2 (v188-1)
Actual Results: "Your SIM card is PUK-locked" error message encountered after correctly entering PUK code and resetting pin
Device: Flame 2.1 (Flame KK - Nightly - Full Flashed)
Build ID: 20150105001204
Gaia: 73be51f998031f06db0cd660c0e388fa621c9f4c
Gecko: 05dd053f1d90
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 34.0 (2.1)
Firmware Version: V18D
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Device: Flame 2.0 (Flame KK - Nightly - Full Flashed)
Build ID: 20150105000200
Gaia: 3c9bb36d9ade1a0acd5e1d6cbb5057be7f5ad484
Gecko: 93f5c85a1d31
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 32.0 (2.0)
Firmware Version: V18D
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Device: Flame Master (V188-1 Flame KK - Nightly - Full Flashed)
Build ID: 20150105010205
Gaia: c2bf20d23851d5fda9f8f0ef0267db5f49152376
Gecko: 636498d041b5
Gonk: a814b2e2dfdda7140cb3a357617dc4fbb1435e76
Version: 37.0a1 (Master)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
-----------------------------------------------------------------------------------
In base 165-only (1.4) The error message given is "The old PIN you typed is not correct. 0 retries left"
Device: Flame 1.4
Build ID: 20140814202332
Gaia: 129211661489feb60bbd6772a44081d23b374f17
Gecko: 1483bd406aad0b3b9e3bdb75c5238b787b5a0cd6
Version: 30.0 (1.4)
Firmware Version: V165
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Reporter | ||
Comment 1•10 years ago
|
||
Flags: needinfo?(pbylenga)
Comment 2•10 years ago
|
||
Not going to nominate to block, not a regression although poor user UX.
Flags: needinfo?(pbylenga)
Updated•10 years ago
|
Blocks: dialer-most-wanted
Comment 3•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•