Closed
Bug 1083991
Opened 10 years ago
Closed 10 years ago
[Email][IMAP] Email app is unable to sign in to IMAP email accounts
Categories
(Firefox OS Graveyard :: Gaia::E-Mail, defect)
Tracking
(b2g-v2.1 unaffected, b2g-v2.2 affected)
RESOLVED
DUPLICATE
of bug 1084245
Tracking | Status | |
---|---|---|
b2g-v2.1 | --- | unaffected |
b2g-v2.2 | --- | affected |
People
(Reporter: Marty, Unassigned)
References
()
Details
(Keywords: regression, smoketest)
Attachments
(2 files)
Description:
If the user attempts to sign in to an IMAP email account (such as Yahoo or Gmail), the device will take a long time at the 'sign in' loading screen, then return the user to the account sign in page with the error message 'Unable to establish a connection with "imap.mail.yahoo.com". There may be a problem with the network"
Repro Steps:
1) Update a Flame device to BuildID: 20141016040204
2) Open the Email app
3) Input the Name and Email Address for a Gmail or Yahoo account and select 'Next'
4) Input the password for the Email account.
Actual:
The account fails to sign in, giving an Network error message.
Expected:
The account signs in properly.
Environmental Variables:
Device: Flame 2.2 Master (319MB)
BuildID: 20141016040204 (Full Flash)
Gaia: 841d0d7d1b879f0ff4b5a8727f5dd23c7b0000a9
Gecko: a280a03c9f3c
Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf
Version: 36.0a1 (2.2 Master)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Repro frequency: 5/5
Link to failed test cases:
https://moztrap.mozilla.org/manage/case/6113/
https://moztrap.mozilla.org/manage/case/6114/
See attached: screenshot, logcat
------------------------------------
This issue does NOT occur on Flame 2.1
Email account signs in properly
Environmental Variables:
Device: Flame 2.1 (319MB)
BuildID: 20141016001201 (Full Flash)
Gaia: 477a9e61c3edf12f32a62a19d329cd277202cc6b
Gecko: 67573e422a0f
Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf
Version: 34.0 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Reporter | ||
Comment 1•10 years ago
|
||
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Comment 2•10 years ago
|
||
[Blocking Requested - why for this release]:
Functional Regression of a Core Feature that fails smoke tests.
Requesting a window.
blocking-b2g: --- → 2.2?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Updated•10 years ago
|
QA Contact: ckreinbring
Updated•10 years ago
|
Comment 3•10 years ago
|
||
These errors from the log seem bad...
10-16 11:38:12.840: W/E-Mail(9483): [JavaScript Error: "Error: Exposing privileged accessor properties is prohibited" {file: "app://email.gaiamobile.org/js/ext/main-frame-setup.js" line: 2}]
10-16 11:38:12.880: W/E-Mail(9483): [JavaScript Error: "Error: Exposing privileged accessor properties is prohibited" {file: "app://email.gaiamobile.org/js/ext/main-frame-setup.js" line: 2}]
10-16 11:38:17.670: I/cat(257): <7>[ 4200.585310] DOM Worker: unhandled page fault (11) at 0xb0f82578, code 0x00f
Comment 4•10 years ago
|
||
Regression window
Last working
BuildID: 20141015110017
Gaia: 841d0d7d1b879f0ff4b5a8727f5dd23c7b0000a9
Gecko: 7de522bd9785
Platform Version: 36.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
First broken
BuildID: 20141015113215
Gaia: 841d0d7d1b879f0ff4b5a8727f5dd23c7b0000a9
Gecko: a280a03c9f3c
Platform Version: 36.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Working Gaia / Broken Gecko = Repro
Gaia: 841d0d7d1b879f0ff4b5a8727f5dd23c7b0000a9
Gecko: a280a03c9f3c
Broken Gaia / Working Gecko = No repro
Gaia: 841d0d7d1b879f0ff4b5a8727f5dd23c7b0000a9
Gecko: 7de522bd9785
Gecko pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=7de522bd9785&tochange=a280a03c9f3c
Mozilla Inbound
Last working
BuildID: 20141015060114
Gaia: 5f1f0960ae9d22acf2a324ad37a48174d6df87f6
Gecko: 1c9d6c298b5a
Platform Version: 36.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
First broken
BuildID: 20141015060614
Gaia: 5f1f0960ae9d22acf2a324ad37a48174d6df87f6
Gecko: 204a676d3c8e
Platform Version: 36.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Working Gaia / Broken Gecko = Repro
Gaia: 5f1f0960ae9d22acf2a324ad37a48174d6df87f6
Gecko: 204a676d3c8e
Broken Gaia / Working Gecko = No repro
Gaia: 5f1f0960ae9d22acf2a324ad37a48174d6df87f6
Gecko: 1c9d6c298b5a
Gecko pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=1c9d6c298b5a&tochange=204a676d3c8e
Comment 5•10 years ago
|
||
Running in firefox nightly, without bundling of scripts, the error line numbers are more informative:
JavaScript error: http://email.gaiamobile.org:8080/js/ext/worker-support/net-main.js, line 84: Error: Exposing privileged accessor properties is prohibited
JavaScript error: http://email.gaiamobile.org:8080/js/ext/worker-support/net-main.js, line 68: Error: Exposing privileged accessor properties is prohibited
Those lines correspond to accessing `event.data` inside some mozTCPSocket event handlers:
https://github.com/mozilla-b2g/gaia/blob/abef62c0623e5504a97b4fd411e879a67b285b52/apps/email/js/ext/worker-support/net-main.js#L68
and
https://github.com/mozilla-b2g/gaia/blob/abef62c0623e5504a97b4fd411e879a67b285b52/apps/email/js/ext/worker-support/net-main.js#L84
This looks like a gecko regression, or at least a non-gaia email regression. The email code has not changed in this area for quite some time.
When the regression range is found, the focus should likely be on changes related to mozTCPSocket or how its event data is exposed to content.
Comment 6•10 years ago
|
||
Broken by bug 1082450 - can you take a look Bobby?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell) → needinfo?(bobbyholley)
Keywords: qaurgent
QA Contact: ckreinbring
Comment 7•10 years ago
|
||
This is bug 1084245. I'm going to talk to jdm about it when he gets in today.
Depends on: 1084245
Flags: needinfo?(bobbyholley)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
blocking-b2g: 2.2? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•