[Settings][Call Barring] Entering the wrong current passcode when changing the Call Barring passcode will not fail until after the user has input a new passcode.

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
4 years ago
4 years ago

People

(Reporter: Marty, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v2.2 affected, b2g-master affected)

Details

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

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8580213 [details]
logcat-call-barring-change-passcode.txt

Description:
When the user attempts to change their Call Barring passcode, they are not informed if they input the wrong current passcode until after they have finished filling out the intended new passcode.  The user will expect to be informed their passcode is wrong immediately after submitting it.

Repro Steps:
1) Update a Flame to 20150319010201
2) Launch the Settings app and navigate to Call Settings > Call Barring
3) Select 'Change passcode'
4) Input an incorrect passcode

Actual:
The user is immediately presented with the 'New passcode' screen, and are not informed they used the wrong passcode until after they attempt to submit the new one.

Expected:
The user is informed they used the wrong passcode before they input the new passcode.

Environmental Variables:
Device: Flame 3.0 (319MB)(Full Flash)
Build ID: 20150319010201
Gaia: c39e15f631de80c69467fda0d4ea0bcda9e194ca
Gecko: cf1060d8ce9f
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 39.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0

Repro frequency: 5/5
See attached: video clip (URL), logcat
(Reporter)

Comment 1

4 years ago
This issue DOES occur on Flame 2.2.
The user is presented with the 'New passcode' screen, and are not informed they used the wrong passcode until after they attempt to submit the new one.

Environmental Variables:
Device: Flame 2.2(319MB)(Full Flash)
Build ID: 20150318002504
Gaia: 306772a58335ac4cad285d27c3805090a8cc6886
Gecko: a6f5f4035ea5
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 37.0 (2.2)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

------------------------

This issue does NOT occur on Flame 2.1.
The Call Barring feature is not implemented in this branch.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Hi Arthur,
This might need your help to investigate.
Flags: needinfo?(arthur.chen)
IIUIC the `changeCallBarringPassword` API requires both the current passcode and the new passcode at the same time, so it is not possible to validate the current passcode first.

Hsinyi, can you help confirm this behavior?
Flags: needinfo?(arthur.chen) → needinfo?(htsai)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
(In reply to Arthur Chen [:arthurcc] from comment #3)
> IIUIC the `changeCallBarringPassword` API requires both the current passcode
> and the new passcode at the same time, so it is not possible to validate the
> current passcode first.
> 
> Hsinyi, can you help confirm this behavior?

The API behaviour is as Arthur mentioned.
Flags: needinfo?(htsai)
Resolve as WONTFIX per comment 4.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.