1093572 - [Flame][Email] Unable to login to a specific EAS Email account.

Status: RESOLVED DUPLICATE of bug 1095144

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[William Hsu [:whsu]]

Attachment: EMAIL_EAS Email account_20141104.log

+++ This bug was initially created as a clone of Bug #1091448 +++

== Issue Description ==
This issue is reported by our partner and can be reproduced on v2.1.

Unable to view messages in a specific EAS Email account when filling in correct username, hostname, password and domain.
The phone successfully connects to the mail, but no messages are shown in the inbox, it just keeps saying "Loading Messages".

 * Demo video: http://youtu.be/F-L4SH21aN8
 * Log: EMAIL_EAS Email account_20141104.log

== STEPS == 
  1) Start Email application
  2) Fill in name & email address & password and proceed to manual setup
  3) Select Account type to ActiveSync and fill in Hostname and Domain\Username
  4) Press Next until you are in the inbox
  5) "Loading messages" appears and no messages are shown

== Actual Result ==
  "Loading messages" appears and no messages are shown.

== Expect Result ==
   Email message list show normally.

== Build Information ==
  @ Tako
   - Gaia-Rev    d056733f8a7a1a152f5458b323f092c47dbffa48
   - Gecko-Rev   df0479fb8c18379488013452e903c33bca384b0d
   - Build ID    20141024145043
   - Version     32.0    
  @ Flame
   - Gaia-Rev    8b0cf889ae0d48a9eb7ecdcb9b67590de45cc5e5
   - Gecko-Rev   https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/388b03efe92d
   - Build-ID    20141104001202
   - Version     34.0

== Reproduce Rate ==
  100%

== Reproducible on Reference phone ==
  Yes

Comment 2

[William Hsu [:whsu]]

[Blocking Requested - why for this release]:

This issue is reported by our partner. Thanks.

Comment 3

[William Hsu [:whsu]]

[Blocking Requested - why for this release]:

Comment 4

[Andrew Sutherland [:asuth] (he/him)]

It looks like my changes to the job completion events made it possible for the "syncblocked" mechanism we use for ActiveSync to end up racing, likely because the job-op and refresh mechanism are largely orthogonal.  This is actually somewhat benign and recoverable (by switching folders probably), but we have the UI indicate that we are still loading for consistency reasons.

Comment 5

[Candice Serran (:cserran)]

broken functionality and regression ->blocking

Comment 6

[Andrew Sutherland [:asuth] (he/him)]

I was wrong in comment 4; my changes to job-ops have no impact on this problem.

The problem is that the syncFolderList operation is failing.  The error code indicates too many devices are already bound to the account.  Because of our change in bug 825538 to create new device id's every time the account is added and it's likely that this account is being for QA purposes, the account has hit its 10 or 100 device limit (or whatever it is).  The account will be usable again if the device mappings are deleted.

I've filed bug 1095144 on having the UI provide an error message when this problem happens.  It's also worth considering mitigations that make the QA process less likely to trigger this problem without compromising privacy, I've filed bug 1095157 on that.

I am duping this bug to bug 1095144 on providing UI for the problem.  I am clearing the blocking flag since this:

- Is not the regression we thought it was.  Things have worked like this since v1.3 and arguably the ability to use more than one Firefox OS device with ActiveSync without experiencing completely random-seeming sync behaviour is very important.

- This is likely to disproportionately affect QA users.  Actual users will only encounter this problem if they keep re-adding the account, like if they keep resetting their device.

- Contacting support will potentially help uncover this error.

Let's concentrate discussion on either of the two bugs I spun off.  We can potentially do some backport-friendly mitigations on that bug too.