977617 - [zffos1.3][P3](Local) After some time the mail service stops working.

Status: RESOLVED INVALID

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

Description

[FangChen]

User Agent: Mozilla/5.0 (Windows NT 6.1; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; TCO_20140227092630; rv:11.0) like Gecko

Steps to reproduce:

   A.- Overview Description (technical background, concise explanation of the bug):
    After some time the mail service stops working.
    
    ________________________________________________________________________________
    B.- Steps to Reproduce (initial conditions, required resources, step by step instructions to reproduce):
    1- Configure a valid e-mail account on the DuT.
2- Write a new e-mail and send it to a valid e-mail.
3- Verify correctly sending of a e-mail.
4- Wait about 30 minutes.
5- Synchronize e-mail manually.
6- See behavior.


Actual results:

 After correctly configure an email account and waiting more than 30 minutes, the mail service stops working and message appears "It could not connect to the server".



Expected results:

The e-mail service must work correctly all the time.

Comment 1

[FangChen]

Built ID :20140218180032
OS version
1.3.0.0-prerelease
QC RIL commit:
a406d321  Add null check when handling set preferred network type
QC RIL TAG version: AU_LINUX_GECKO_B2G_JB_3.2.01.03.00.112.223

gaia commit:
744fb691 Merge pull request #15526 from steveck-chung/bug-961231

gecko commit:
6840e8c2 Bumping gaia.json for 1 gaia-1_3 revision(s) a=gaia-bump

Comment 2

[Jason Smith [:jsmith]]

Can someone on the Moz side confirm this?

Comment 3

[Juan Perez-Bedmar [:juanpbf]]

Is there any update here? Has anyone in Moz been able to reproduce this issue?

Comment 4

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

A logcat and the other information from https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo is required in all cases.  For example, it's very important to know the e-mail domain being used.  We recently landed a fix for a gmail-specific issue on bug 977867 which could explain this if the account being used is gmail.

Comment 5

[sarsenyev]

I was able to reproduce it, just without "error message"
After 30 min tried to sync email manually, the "sync" icon is continuing spinning without updating, to be able to sync it the user needs to close the app and reopen again

Steps:
1.) Log into Gmail account gmail.com/IMAP
2) Send email from another account to the DUT
3) Wait 30 minutes and then manually sync the email

1.3 Environmental Variables:
Device: Buri 1.3 MOZ
BuildID: 20140318004002
Gaia: 2ea2aab306bd1c941719160cdcb49ee9d755dc17
Gecko: cf2042938526
Version: 28.0
Firmware Version: v1.2-device.cfg

Comment 6

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

Do you have a logcat from your reproduction run?

Comment 7

[Jason Smith [:jsmith]]

QA Wanted to get a logcat.

Comment 8

[Natalya Kot [:nkot]]

I've been watching this bug during the day, having two 1.3 devices on the side (Buri and Open_C), sending emails there and manually syncing emails every 30-40 min and I haven't seen any server errors as per comment 0. I also talked to Sergey (comment 5) and I believe his issue was different from the original bug and he's unable to repro it anymore. 

So we can't provide the logcat with the issue and we cannot confirm that the issue is reproducible in the first place.

I've tested with both Gmail and Hotmail accounts.
 
Buri 1.3
BuildID: 20140326004002
Gaia: 812838ad0fabf51fa14435af562ddac6d26fa936
Gecko: ba97efb0da4b
Version: 28.0
Firmware Version: v1.2-device.cfg

Open_C 1.3
Build ID: 20140326040052
Gecko: db0c8822aeafe9038815bdadf6d4312927cef250
Gaia: be872843fa702e25ba113a93ce84fd8b265d87fb
Base Image: P821A10-ENG_20140321

Comment 9

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

Thanks for all the repro efforts.  I'm going to declare this invalid on the basis that we basically have no idea what the root cause was without a logcat or much more detailed steps-to-reproduce and explicit error messages and codes (so WFM is inappropriate).  Since there is reason to suspect bug 977867 could have been at fault and there is nothing actionable at this time, I think it makes sense to close out.

Reporter, if you are able to reproduce the problem, please feel free to reopen this bug or a new bug, but please be sure to provide the information requested on https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo.