Closed
Bug 1173185
Opened 9 years ago
Closed 9 years ago
[B2GDroid] Unable to login with Email app.
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(b2g-master unaffected)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
b2g-master | --- | unaffected |
People
(Reporter: jthomas, Unassigned)
References
()
Details
(Whiteboard: [3.0-Daily-Testing])
Attachments
(2 files)
Description: The user is unable to login into their Email using the Email app.
Repro Steps:
1) Update to B2GDroid 20150608071805
2) Select Email App
3) Fill in Name and Email address. (You may be prompted to fill in information twice.)
4) Select Next (Endless "Setting up account" message appears)
5) Sometimes selecting cancel the Error message as seen in the screenshot occur.
Actual:
An endless "Setting up account" message appears. Or the error as seen in the screenshot.
Expected:
It is expected that the user will be able to login to their email.
Repro frequency: 100%.
See attached: Logcat, Screenshot & Video
Reporter | ||
Comment 1•9 years ago
|
||
Reporter | ||
Comment 2•9 years ago
|
||
Additional note: The email used for the logcat was my work email. I understand that Imaps must be enabled in order for my email to work. However, after submitting this bug I tried with an alternative email and received the same results on the droid.
This issue does NOT occur on the Flame 3.0.
Result:
User is able to login with a valid Email.
Environmental Variables:
Device: Flame 3.0 Kitkat Fullflash (319mb)
Build ID: 20150608160934
Gaia: ea27c4ed5b6083c9e21d233d4804372ac4d5d353
Gecko: e10e2e8d8bf2
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Blocks: b2gdroid
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-master:
--- → unaffected
Flags: needinfo?(ktucker)
Whiteboard: [3.0-Daily-Testing]
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(ktucker)
You need to log in
before you can comment on or make changes to this bug.
Description
•