Closed
Bug 1068356
Opened 10 years ago
Closed 10 years ago
Authentication screen remains indefinitely when long tapping on the homescreen button in the FxAccount login proccess
Categories
(Firefox OS Graveyard :: FxA, defect)
Tracking
(blocking-b2g:2.0+, b2g-v2.0 fixed, b2g-v2.0M fixed, b2g-v2.1 fixed, b2g-v2.2 fixed)
People
(Reporter: oteo, Assigned: ferjm)
References
Details
(Whiteboard: [platform][blocking])
Attachments
(1 file)
46 bytes,
text/x-github-pull-request
|
alive
:
review+
bajaj
:
approval-gaia-v2.0+
fabrice
:
approval-gaia-v2.1+
|
Details | Review |
Bug reported by Javier in Comment 10 of bug 1045568 but we need to track separately.
Device: Flame
Loop version: c28eaef
Build: flame-kk.user.v2.0.gecko-2d2ca12.gaia-7edd3b0
1.- Sign out from Settings->FxAccounts
2.- Open Loop, and try to log-in with FxAccount
3.- Try to change to another app (long tap home button)
ACTUAL RESULT
Loop is permanently blocked trying to authenticate.
EXPECTED RESULT
Return to the main loop screen.
Reporter | ||
Updated•10 years ago
|
Severity: normal → critical
Priority: -- → P1
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → ferjmoreno
Assignee | ||
Updated•10 years ago
|
Component: Gaia::Loop → FxA
Reporter | ||
Updated•10 years ago
|
Whiteboard: [platform][blocking]
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8491461 -
Flags: review?(alive)
Assignee | ||
Comment 3•10 years ago
|
||
[Blocking Requested - why for this release]: This makes users to be blocked in apps like Loop that blocks the UI while the FxA flow is being executed and expect a result from this flow. Without this patch, this result will never be given to the app and so the user will be blocked until the app is restarted via task manager.
blocking-b2g: --- → 2.1?
Reporter | ||
Comment 4•10 years ago
|
||
[Blocking Requested - why for this release]: Same than above, already explained by Fernando, just changing that we need this fix for 2.0 as Loop Mobile Client is going to be launched on that version
blocking-b2g: 2.1? → 2.0?
Assignee | ||
Comment 5•10 years ago
|
||
Alive, I also took the chance to do the proper clean up of the mobile ID dialog as we do with the FxA one.
Reporter | ||
Updated•10 years ago
|
Priority: P1 → --
Whiteboard: [platform][blocking] → [platform][blocking][patch available]
Comment 7•10 years ago
|
||
Comment on attachment 8491461 [details] [review]
Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/24178
r=me
Attachment #8491461 -
Flags: review?(alive) → review+
Assignee | ||
Comment 8•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
QA Contact: aalldredge
Comment 9•10 years ago
|
||
This issue is occurring on 2.1 Flame, 2.0 Flame, and 2.0 Flame Base.
Environmental Variables:
Device: Flame 2.1
BuildID: 20140919105218
Gaia: d558bd001edee9defa017bd67551d43878077932
Gecko: 0d23cb46b0f3
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Device: Flame 2.0
BuildID: 20140919041249
Gaia: 31434a3949556171f3565ca47ac2b44e810e95e6
Gecko: fb1589259e4f
Version: 32.0 (2.0)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Device: Flame 2.0
BuildID: 20140904160718 (Base)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Result:
Opening card view while authenticating prevents the process from completing.
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Assignee | ||
Comment 10•10 years ago
|
||
Comment on attachment 8491461 [details] [review]
Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/24178
[Approval Request Comment]
[Bug caused by] (feature/regressing bug #): FxA system dialog
[User impact] if declined: his makes users to be blocked in apps like Loop that blocks the UI while the FxA flow is being executed and expect a result from this flow. Without this patch, this result will never be given to the app and so the user will be blocked until the app is restarted via task manager.
[Testing completed]: Manual tests done and unit tests added
[Risk to taking this patch] (and alternatives if risky): Low risk
[String changes made]: None
Attachment #8491461 -
Flags: approval-gaia-v2.1?
Attachment #8491461 -
Flags: approval-gaia-v2.0?
Comment 11•10 years ago
|
||
Bhavana-
Please see approval/blocking requests from above.
Flags: needinfo?(bbajaj)
Updated•10 years ago
|
Attachment #8491461 -
Flags: approval-gaia-v2.1? → approval-gaia-v2.1+
Comment 12•10 years ago
|
||
status-b2g-v2.2:
--- → fixed
Whiteboard: [platform][blocking][patch available] → [platform][blocking]
Target Milestone: --- → 2.1 S5 (26sep)
Comment 13•10 years ago
|
||
Triage group reviewed, blocking+ due to broken new feature and low risk landing.
blocking-b2g: 2.0? → 2.0+
Updated•10 years ago
|
Flags: needinfo?(bbajaj)
Updated•10 years ago
|
Attachment #8491461 -
Flags: approval-gaia-v2.0? → approval-gaia-v2.0+
Comment 14•10 years ago
|
||
Comment 15•10 years ago
|
||
status-b2g-v2.0M:
--- → fixed
Comment 16•10 years ago
|
||
Verified on flame (Gecko-b3429ef.Gaia-c6c6116) and fireE (firee-kk-v2.0-SW2E3-1)
Loop version: 1.1 , 2168965
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•