[E-Mail] IMAP error from Sign-In lingers when attempting to setup another account; must complete an account to dismiss error

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
4 years ago
10 months ago

People

(Reporter: onelson, Unassigned)

Tracking

({polish})

unspecified
ARM
Gonk (Firefox OS)
polish

Firefox Tracking Flags

(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)

Details

(Whiteboard: [3.0-Daily-Testing], URL)

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Description:
When a user attempts to sign in an e-mail address and receives an error, a banner will display over the root page of E-Mail (example "You must enable IMAP for your Gmail account.") This error message will not dismiss until a successful e-mail account login occurs. Note that if this is NOT the first email you have attempted to sign in and you accessed this page through 'Add Account' in 'Settings' from a logged in E-mail, dismissing the 'Add Account' page and returning will not display the error banner as expected.
   
PreReq:
* prepare an email address that will produce an error; tested against a gmail account with IMAP enabled.
Repro Steps:
1) Update a Flame device to BuildID: 20150121010204
2) Open 'E-Mail' app.
3) Enter credentials for email address that follows prequisite listed above.
4) Attempt to sign in through automatic process.
5) Observe error banner that occurs.
6) Enter new credentials for a succesful email account.
7) Tap 'Next', observe 'Setting up Account'.
8) Don't enter password, instead return to 'E-Mail' root page.
  
Actual:
Error banner lingers until a new e-mail account is successfully signed in.
  
Expected: 
Error banner is dismissed once a new account is attempted to sign in, as it may not be pertinent to the next e-mail the user attempts.
  
Environmental Variables:
Device: Flame 3.0 Master
BuildID: 20150121010204
Gaia: 5e98dc164b17fd6decb48a9eaddef0e55b82e249
Gecko: 540077a30866
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 38.0a1 (3.0 Master)
Firmware: V18D-1
User Agent: Mozilla/5.0 (Mobile; rv:38.0) Gecko/38.0 Firefox/38.0
  
  
Repro frequency: 5/5
See attached: 
video- http://youtu.be/Hs5NKsYk8X8
logcat
(Reporter)

Comment 1

4 years ago
Issue DOES NOT REPRO in flame 2.2 devices (different behaviour is observed):

PreReq:
* prepare an email address that will produce an error; tested against a gmail account with IMAP 
Results: When a user attempts to sign-in a new e-mail addressed by the prequisite above, they will be taken to 'Manual Setup' instead of automatic, which upon conclusion will produce the same error in the 'Manual Setup' page. Leaving this page will dismiss the error, and returning to that page will not have the error present. (May be another bug?)

Environmental Variables:
----------------------------------------------
Device: Flame 2.2
BuildID: 20150121002607
Gaia: e4f9b5da3751798f9cc5d95f302c30722cc11fca
Gecko: 75a462a58d7a
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 37.0a2 (2.2)
Firmware: V18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
----------------------------------------------
Repro Rate: 3/3
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Whiteboard: [3.0-Daily-Testing]
(Reporter)

Comment 2

4 years ago
Created attachment 8552785 [details]
logcat_20150121_1616.txt

Attaching logcat for comment#0
(Reporter)

Updated

4 years ago
status-b2g-v2.2: --- → unaffected
[Blocking Requested - why for this release]:
Identifiable regression.

Requesting a window.
blocking-b2g: --- → 3.0?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Keywords: regression, regressionwindow-wanted
QA Contact: ktucker
(Reporter)

Comment 4

4 years ago
Updating my own comment#1:
This issue REPROES on flame 2.2, 2.1 and 2.0 devices

PreReq:
* prepare an email address that will produce an error; tested against a gmail account with IMAP 
Results: Error banner lingers until a new e-mail account is successfully signed in.

Environmental Variables:
----------------------------------------------

Device: Flame 2.2
BuildID: 20150122002808
Gaia: e4f9b5da3751798f9cc5d95f302c30722cc11fca
Gecko: 4a90da67661e
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 37.0a2 (2.2)
Firmware: V18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

----------------------------------------------

Device: Flame 2.1
BuildID: 20150122001404
Gaia: 2055fc40a8bd2af1908979cb45da6b7d1c4ced0b
Gecko: 38ac70ca969b
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 34.0 (2.1)
Firmware: V18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

----------------------------------------------

Device: Flame 2.0
BuildID: 20150122000201
Gaia: 736933b25ded904f0cb935a0d48f1f3cf91d33ad
Gecko: 296e19e6edcb
Gonk: e7c90613521145db090dd24147afd5ceb5703190
Version: 32.0 (2.0)
Firmware: V18D-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
----------------------------------------------

Repro: 3/3

This demonstrates that my previous assertion was actually a separate bug that is not presently reproducing. I'll work to investigate it when I find a moment. Removing the regression keyword and the the nomination for blocking.
blocking-b2g: 3.0? → ---
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0: --- → affected
status-b2g-v2.1: --- → affected
status-b2g-v2.2: unaffected → affected
Flags: needinfo?(pbylenga)
Keywords: regression, regressionwindow-wanted
In that case,nominating for polish work.  I'd expect us to dismiss the banner on transitioning away from the screen that displays it.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Keywords: polish

Comment 6

4 years ago
Is this email specific? What email address will produce an error?
NI on Oliver for Comment 6.
Flags: needinfo?(onelson)
(Reporter)

Comment 8

4 years ago
The email address I had used was my own account for work: onelson@qanalydocs.com
The @qanalydocs domain utilizes gmail, but is not setup for IMAP protocol, so upon failing will return the user to the root page of email with an IMAP banner error. That error follows the results above, and will not dismiss until the app is closed, or a successful login is performed.
Flags: needinfo?(onelson) → needinfo?(pbylenga)
Flags: needinfo?(pbylenga)

Comment 9

10 months ago
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.