Closed
Bug 927243
Opened 11 years ago
Closed 10 years ago
[Buri][TOR][Email]Recreate email account,send email failed when network is normal
Categories
(Firefox OS Graveyard :: Gaia::E-Mail, defect, P1)
Firefox OS Graveyard
Gaia::E-Mail
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 926751
People
(Reporter: sync-1, Unassigned)
Details
Attachments
(3 files)
Firefox os v1.1 Mozilla build ID:20130916041201 Created an attachment (id=537921) logcat.log DEFECT DESCRIPTION: Recreate email account,send email failed when network is normal REPRODUCING PROCEDURES: 1.First email account creation was OK 2. Then sending/receiving was OK 100% 3.Delete the account 4.Re create it 5. The sending/reception is working 20%-->KO EXPECTED BEHAVIOUR: Send email successfully when network is normal. ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: high REPRODUCING RATE: 2/5 For FT PR, Please list reference mobile's behavior:
Comment 2•11 years ago
|
||
This looks like a similar problem to bug 926751; the network connection changes and our conneciton dies. Except in this log, we seem to sometimes accomplish some of our goals before the connection dies.
Dear Andrew, Yes, this is the same as problem descripted in https://bugzilla.mozilla.org/show_bug.cgi?id=926751#c15, but I think bug#926751 should focus on 3g network. What do you think? Thanks.
blocking-b2g: --- → leo?
Summary: [Buri][Telenor][Email]Recreate email account,send email failed when network is normal → [Buri][TOR][Email]Recreate email account,send email failed when network is normal
Comment 6•11 years ago
|
||
NI on :mvines to help with next steps here ? Would https://bugzilla.mozilla.org/show_bug.cgi?id=926751#c88 resolve this issue as well ?
Flags: needinfo?(mvines)
Comment 9•10 years ago
|
||
triage: Resolving as a duplicate of 926751 based on comment #7 here and https://bugzilla.mozilla.org/show_bug.cgi?id=926751#c88
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
blocking-b2g: 1.4? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•