Closed Bug 881167 Opened 11 years ago Closed 11 years ago

Clicking "Cancel" from the persona screen after a PIN lockout hangs with "Connecting to Persona.."

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P2)

Other
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED FIXED
2013-07-11

People

(Reporter: krupa.mozbugs, Assigned: wraithan)

References

Details

(Whiteboard: [blocked on 1.1 uplift])

Attachments

(2 files)

steps to reproduce:
1. Start the purchase of a paid app
2. Log in using Identity
3. Enter your PIN incorrectly for 5 times
4. Notice the error message - "You have entered your PIN incorrectly too many times.."
5. Click reset PIN button
6. When user is asked to log in with Persona, click Cancel

expected behavior:
User returns to marketplace

actual behavior:
user is stuck with a "connecting to persona" loading screen.
That string does not exist in the code base. Please provide a screenshot of the page. The screen that should appear after incorrectly entering your pin should only have a 'OK' button on it.
Flags: needinfo?(krupa.mozbugs)
Flags: needinfo?(krupa.mozbugs)
Ahh, between 3 and 4 in the STR should be 'wait 5 mins for your pin to unlock'
Assignee: nobody → wraithan
Priority: -- → P2
Component: Consumer Pages → Payments/Refunds
Clicking cancel on any persona login does this. Not just during reset pin.
Just for reference, the parent github bug is

https://github.com/mozilla/browserid/issues/3456

But! That github bug links back to a bugzilla bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=881014
(In reply to Jared Hirsch [:_6a68] from comment #7)
> Just for reference, the parent github bug is
> 
> https://github.com/mozilla/browserid/issues/3456
> 
> But! That github bug links back to a bugzilla bug:
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=881014

Correct.  When bug 81014 gets uplift, this will be fixed.
Depends on: 881014
Whiteboard: [blocked on 1.1 uplift]
(In reply to Jed Parsons [:jparsons] from comment #8)

> Correct.  When bug 81014 gets uplift, this will be fixed.

A digit got dropped.  The correct bug, as you have all correctly inferred, is Bug 881014.
status-b2g-v1.1hd: affected → fixed

On the parent bug, going to test this and see if it is fixed.
Flags: affects-moss+
Flags: affects-tricycle+
Flags: affects-seville+
Flags: affects-seahorse+
Flags: affects-durango+
For 1.0.1 devices this was WONTFIX for 1.1 devices this was fixed.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-07-11
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: