Closed
Bug 1068064
Opened 10 years ago
Closed 7 years ago
[Loop] Loop client crashes when user log-in into the app following the wizard (first time user uses the app) with Firefox Account (not previously registered in settings)
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: javier.deprado, Unassigned)
References
Details
(Whiteboard: [mobile app][tef-triage])
Attachments
(1 file)
16.00 KB,
text/plain
|
Details |
Device: Flame
Loop version: c28eaef
Build: flame-kk.user.v2.0.gecko-2d2ca12.gaia-7edd3b0
1.- Install Loop client
2.- Check in settings-> Firefox Accounts you're not authenticated
2.- Open Loop, and and once the wizard has completed, try to login using Firefox Accounts
3.- At the end of the process,by pressing the button "Done", Loop app crashes.
ACTUAL RESULT
Loop crashes.
EXPECTED RESULT
main screen of the application should appear.
Reporter | ||
Updated•10 years ago
|
Whiteboard: [mobile app]
Updated•10 years ago
|
Hardware: x86 → ARM
Updated•10 years ago
|
Severity: normal → critical
Priority: -- → P1
Comment 1•10 years ago
|
||
It seems that it does not happen with all the devices, so we need to ensure that it happens or not when the app is uploaded in the Market Place.
Priority: P1 → --
Whiteboard: [mobile app] → [mobile app][blocking][tef-triage]
Updated•10 years ago
|
Assignee: nobody → carmen.jimenezcabezas
Updated•10 years ago
|
Status: NEW → ASSIGNED
Comment 3•10 years ago
|
||
FxA folks are working on the 401 issue at https://github.com/mozilla/jwcrypto/issues/95
Comment 4•10 years ago
|
||
Besides the 401 error, I was seeing a pretty consistent crash on my Flame when trying to log in. After debugging it, I determined it was an OOM error... and then remembered I had my flame configured to simulate 256Mb devices. After resetting the Flame configured memory to 512, the crashes disappeared. Since I believe 256Mb devices are not going to be supported anyway, closing this as duplicated.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 5•10 years ago
|
||
This is not going to happen in 1.1 target customer, so not blocking and moving to be considered in next version
Whiteboard: [mobile app][blocking][tef-triage] → [mobile app][tef-triage]
Updated•10 years ago
|
Severity: critical → major
Updated•9 years ago
|
Assignee: carmen.jimenezcabezas → nobody
Comment 6•7 years ago
|
||
Firefox OS is not being worked on
Status: REOPENED → RESOLVED
Closed: 10 years ago → 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•