Closed
Bug 1053414
Opened 10 years ago
Closed 10 years ago
[B2G][Loop] When signing back in to Firefox Accounts, the user will go into an automatic call
Categories
(Firefox OS Graveyard :: Gaia::Loop, defect)
Tracking
(b2g-v2.0 affected, b2g-v2.1 affected)
RESOLVED
DUPLICATE
of bug 1058706
People
(Reporter: psiphantong, Unassigned)
References
()
Details
(Whiteboard: [blocking][2.0-exploratory])
Attachments
(1 file)
267.32 KB,
text/plain
|
Details |
Description:
When the user logout and signs back in to Firefox Accounts, the user will go into an automatic call
Setup:
- Install the Loop app on two devices from: https://github.com/mozilla-b2g/firefoxos-loop-client
- Sign into Loop app using Firefox Accounts
Repro Steps:
1) Update a Flame (319mb) to 20140813000201
2) Go to the Loop App
3) Have a recent call in the log
4) Logout and log back in Firefox Accounts
Actual:
User gets an automatic call
Expected:
User does not get an automatic call
Environmental Variables:
Device: Flame 2.0 (319mb)
BuildID: 20140813000201
Gaia: cade2fdbb2230670788dcf2fc7b100f4a37b6458
Gecko: a7c673dae1ed
Version: 32.0 (2.0)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Repro frequency: 3/3
See attached: video and logcat attached, https://www.youtube.com/watch?v=JCe0TkDGSHs
Reporter | ||
Comment 1•10 years ago
|
||
This issue also reproduce on Flame 2.1 (319mb), Flame 2.0 (512mb). User gets an automatic call.
Flame 2.1 (319mb)
Environmental Variables:
Device: Flame Master
Build ID: 20140812040201
Gaia: e78e62125eb43c3a28cdc047987ba54430694a2f
Gecko: b53c2753ce9a
Version: 34.0a1 (Master)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Flame 2.0 (512mb)
Environmental Variables:
Device: Flame 2.0
Build ID: 20140812000205
Gaia: 1144cdc3a544f81c9bf71598aba1cb67d6c95a29
Gecko: 6495a7bd61ed
Version: 32.0 (2.0)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
_________________________________________________________________________________________________________________________
This issue does not reproduce on the Flame 1.4 because the feature was not supported.
Flame 1.4 (319mb)
Environmental Variables:
Device: Flame 1.4
Build ID: 20140812063005
Gaia: ec395d47cee9234ae93d2410d8ef8724dfc5d6cb
Gecko: 5b219153e2f4
Version: 30.0 (1.4)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
______________________________________________________________________________________________________
Testers were informed not to test on Buri devices
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Comment 2•10 years ago
|
||
mbarone, can you please weigh in on the severity of this issue? Seems like it would be a possible blocker.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(mbarone976)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Comment 3•10 years ago
|
||
This seems to be related (if not the same) to bug 1058706. At least the root cause is likely to be the same.
Whiteboard: [2.0-exploratory] → [blocking][2.0-exploratory]
Updated•10 years ago
|
Flags: needinfo?(mbarone976)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•