Closed
Bug 963037
Opened 12 years ago
Closed 12 years ago
[FTE] When I insert three times invalid PIN I can't see PUK1 screen
Categories
(Firefox OS Graveyard :: Gaia::First Time Experience, defect)
Tracking
(blocking-b2g:1.3+, b2g-v1.3 fixed)
Tracking | Status | |
---|---|---|
b2g-v1.3 | --- | fixed |
People
(Reporter: oteo, Assigned: qdot)
Details
(Whiteboard: [systemsfe])
Attachments
(1 file)
Pre-requisites:
SIM with active PIN without entering the PIN before
Opening this bug as suggested in comment 11 in Bug 961746
Steps:
1. Lanch FTE
2. Insert three times an invalid PIN
Expect result:
See PUK screen
Actual result:
PUK screen is not shown, you can enter more than 3 times the incorrect PIN
Comment 2•12 years ago
|
||
Dupe of a blocker.
Status: NEW → RESOLVED
blocking-b2g: 1.3? → 1.3+
Closed: 12 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•12 years ago
|
||
(In reply to Andrew Overholt [:overholt] from comment #2)
> Dupe of a blocker.
>
> *** This bug has been marked as a duplicate of bug 961746 ***
Hi Andrew,
I created this bug becuse Arthur told me in bug 961746 (the one marked as duplicated) that FTE handles sim card lock by itself and suggested me to open a new bug reporting the fault in the FTE.
Requesting ni to Andrew to confirm it
Flags: needinfo?(arthur.chen)
Comment 4•12 years ago
|
||
Okay - I saw the comment in the other bug. The implementation work would be different here than bug 961746, so I'll reopen to track a fix in the FTE app.
Status: RESOLVED → REOPENED
Flags: needinfo?(arthur.chen)
Resolution: DUPLICATE → ---
Assignee | ||
Comment 5•12 years ago
|
||
Repro verified on master. Looks like we never actually check to see what the card state is after pin entry failures.
Assignee: nobody → kyle
Assignee | ||
Comment 6•12 years ago
|
||
Attachment #8367751 -
Flags: review?(mhenretty)
Assignee | ||
Comment 7•12 years ago
|
||
It seems like it'd be better to see if cardState flipped from pinRequired to pukRequired, but that doesn't seem to be happening when I check mozIcc.cardState. So, we just watch for the retries to hit 0.
Comment 8•12 years ago
|
||
(In reply to Kyle Machulis [:kmachulis] [:qdot] from comment #7)
> It seems like it'd be better to see if cardState flipped from pinRequired to
> pukRequired, but that doesn't seem to be happening when I check
> mozIcc.cardState. So, we just watch for the retries to hit 0.
Yeah, the card state update is not immediate. That's why we have to do this when unlocking:
https://github.com/mozilla-b2g/gaia/blob/6b5ab7b303747c6356c71a4e0fbeba6ec0cb7471/apps/communications/ftu/js/sim_manager.js#L559
Updated•12 years ago
|
Attachment #8367751 -
Flags: review?(mhenretty) → review+
Assignee | ||
Comment 9•12 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 10•12 years ago
|
||
Uplifted fbe5fb9710530d2d540d626852b6599387ec53a4 to:
v1.3: 8dcbb45aeb6378391ac779fe82f1bc2d9af4eefd
status-b2g-v1.3:
--- → fixed
Comment 11•12 years ago
|
||
Tested (02/03/2014) and working
1.3
Gecko 3c269ae
Gaia f9a37c7
Status: RESOLVED → VERIFIED
Updated•12 years ago
|
Whiteboard: [systemsfe]
Target Milestone: --- → 1.3 C3/1.4 S3(31jan)
You need to log in
before you can comment on or make changes to this bug.
Description
•