Closed
Bug 1074345
Opened 10 years ago
Closed 10 years ago
Email syncing not working
Categories
(Firefox OS Graveyard :: Gaia::E-Mail, defect)
Tracking
(tracking-b2g:+, b2g-v2.0 unaffected, b2g-v2.0M unaffected)
RESOLVED
DUPLICATE
of bug 1018828
tracking-b2g | + |
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | unaffected |
b2g-v2.0M | --- | unaffected |
People
(Reporter: gwagner, Unassigned)
Details
(Whiteboard: [priority])
Maybe 1 out of 5 times the manual syncing doesn't work on 2.1. It shows 'Last sync: just now" but no new emails are shown. I have to kill the app and restart to see new messages.
Reporter | ||
Comment 1•10 years ago
|
||
[Blocking Requested - why for this release]:
blocking-b2g: --- → 2.1?
Comment 2•10 years ago
|
||
For these kinds of problems, it is best if we can get a logcat of what email was doing when it failed, since it can be related to a specific email message fetch.
Some info on how to do that is here: https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo (the "A log of what was happening..." section).
Flags: needinfo?(anygregor)
Comment 3•10 years ago
|
||
I think what's probably happening here is that 1) we're encountering an error in the sync process and 2) we're updating the user-visible timestamp anyways. Specifically in ImapFolderSyncer._lazySyncDateRange we call FolderStorage.markSyncRange in $imapsync.Sync.oncomplete regardless of whether we encountered any errors. We do this because we do need to call markSyncRange even for partial sync successes for invariant correctness purposes. When we added folderMeta.lastSyncedAt it was placed in markSyncRange for convenience purposes since it was centralized.
It's not clear if we should change the second thing or not. Specifically, if I'm a user and sync isn't working right, I think I'm going to be frustrated if we claim to not have synchronized or if we claim to have synchronized. I suppose going forward we could alter the string to indicate a failure, ex: "Failed sync: just now."
But mainly we just need to fix whatever the sync error is, so a logcat would indeed be invaluable. I realize you're dog-fooding, so in the event you don't get one, we can probably try and repro on mozilla.com accounts.
One Q for Gregor though; do you normally leave the email app active in the background? Or do you close it so that it can open itself and close itself in the background without hanging around? Knowing whether this is more likely to be an accumulated error or not will help in reproducing.
Reporter | ||
Comment 4•10 years ago
|
||
(In reply to Andrew Sutherland [:asuth] from comment #3)
> One Q for Gregor though; do you normally leave the email app active in the
> background? Or do you close it so that it can open itself and close itself
> in the background without hanging around? Knowing whether this is more
> likely to be an accumulated error or not will help in reproducing.
I usually close the email app manually.
Flags: needinfo?(anygregor)
Comment 5•10 years ago
|
||
Adding qawanted to get a logcat for this issue and for branch checks.
Keywords: qawanted
Comment 6•10 years ago
|
||
high priority bug. Asuth to look but not blocking
blocking-b2g: 2.1? → backlog
Whiteboard: [priority]
Comment 7•10 years ago
|
||
I'm unable to reproduce this bug on a 9/29 Flame 2.1 engineering build. Manual sync'ing (tapping on the circular icon on bottom left) correctly synced new emails in all attempts. Repro rate: 0/20
Tested on:
Device: Flame (shallow flash)
BuildID: 20140929004258
Gaia: 063de64a4ffc606e931ed7b09e93282713c46eca
Gecko: 5d0ec7211d63
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Leaving qawanted tag for others to attempt.
Bug 1080036 may be related.
Comment 10•10 years ago
|
||
Hi KTucker,
Unable to reproduce this bug on a 10/20 Flame 2.0 engineering build. Manual sync'ing (tapping on the circular icon on bottom left) correctly synced new emails in all attempts. Repro rate: 0/20
Test version:
Gaia-Rev 9c7dec14e058efef81f2267b724dad0850fc07e4
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/c17df9fe087d
Build-ID 20141019160201
Version 32.0
Device-Name flame-kk
FW-Release 4.4.2
FW-Incremental 34
FW-Date Tue Sep 30 14:06:36 CST 2014
Bootloader L1TC00011840
-----------------------
Gaia-Rev a273ab9c18e9184eb02722b25c73e2ba7680cc09
Gecko-Rev e7df4dde2d9dbedee942333d34eaea2afe32bebc
Build-ID 20141017100433
Version 32.0
Device-Name soul35
FW-Release 4.4.2
FW-Incremental 1413510704
FW-Date Fri Oct 17 09:52:15 CST 2014
"
Updated•10 years ago
|
status-b2g-v2.0:
--- → unaffected
status-b2g-v2.0M:
--- → unaffected
Comment 11•10 years ago
|
||
Since this bug didn't get any logs or anything distinctive going on, duping to Lucas's similar bug which we'll track as a sort-of meta bug for this still.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•10 years ago
|
blocking-b2g: backlog → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•