Closed
Bug 901992
Opened 11 years ago
Closed 11 years ago
B2G MMS: Retry Mechanism for Downloading MMS is Buggy
Categories
(Firefox OS Graveyard :: General, defect, P1)
Tracking
(blocking-b2g:leo+, firefox24 wontfix, firefox25 wontfix, firefox26 fixed, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 wontfix, b2g-v1.1hd fixed, b2g-v1.2 fixed)
People
(Reporter: airpingu, Assigned: airpingu)
References
Details
(Whiteboard: [leo-triage])
Attachments
(1 file)
3.11 KB,
patch
|
vicamo
:
review+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #840066 +++ Sometimes, the downloading circle is just spinning forever when retrieving MMS either by automatic or manual. After looking into the retry mechanism, I found out there are some bugs stopping the retry mechanism working well. Thanks Julien for discovering this! Let's fix it! Hi Joe, we need to mark this as LEO+ because it blocks bug 840066 which is an important feature.
Assignee | ||
Comment 1•11 years ago
|
||
We have two bugs: 1. The binding for the second retry is wrong. I rewrite the logic just like the sending retry. 2. s/id/savableMessage.id/ to make it update the delivery status correctly.
Attachment #786351 -
Flags: review?(vyang)
Comment 2•11 years ago
|
||
Please clarify the following: 1) What is the reproducible rate? 2) How easy is it to recover the message post this failure?
Flags: needinfo?(gene.lian)
Assignee | ||
Comment 3•11 years ago
|
||
(In reply to Preeti Raghunath(:Preeti) from comment #2) > Please clarify the following: > 1) What is the reproducible rate? This issue only happens when the platform fails to download the MMS, which could depend on the MMSC and network status. However, we can still reproduce the bug in an alternative way, which can has an 100% reproducing rate: 1. Settings -> Message Settings -> Auto retrieve -> Off -> OK. 2. Send an MMS to self and get an message for manual download. 3. Turn on the airplane mode in the settings. 4. Tap on the download button. 5. The downloading circle will keep spinning forever even after the 4 times retries (totally 2560 seconds later [1]). The expected behaviour is the spinning circle should become exclamation mark eventually. [1] The platform has an automatic retry mechanism internally, which will try at most 4 times until the MMS is successfully downloaded. The time interval between each retry is 60, 300, 600, 1800 seconds respectively. > 2) How easy is it to recover the message post this failure? I don't understand this question.
Flags: needinfo?(gene.lian)
Comment 4•11 years ago
|
||
(In reply to Gene Lian [:gene] from comment #3) > (In reply to Preeti Raghunath(:Preeti) from comment #2) > > 2) How easy is it to recover the message post this failure? > > I don't understand this question. After some time (about 1 day, maybe it was because I rebooted), I actually get the exclamation mark and then I can retry downloading the message, which eventually works.
Assignee | ||
Comment 5•11 years ago
|
||
Correct. You can get an exclamation mark again by rebooting. We fix this bug by correctly updating the delivery status at run-time if the MMS fails to download after all the retries.
Updated•11 years ago
|
Attachment #786351 -
Flags: review?(vyang) → review+
Assignee | ||
Comment 6•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/13d9724f03b1
Comment 7•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/13d9724f03b1
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Whiteboard: [l
Comment 8•11 years ago
|
||
Triage - not a blocker by partner. Leaving moz triage to decide.
Whiteboard: [l → [leo-triage]
Comment 9•11 years ago
|
||
This is a real bug that happens quite often in real life (from a dogfood user). Gene> could it be possible to write a testcase for this bug ?
Comment 10•11 years ago
|
||
It does work to retry at some point and without a partner champion we won't block v1.1 on this at this stage. Bumping to koi? so this might get a higher priority in v1.2.
blocking-b2g: leo? → koi?
Assignee | ||
Comment 11•11 years ago
|
||
Hoping to uplift this to V1.1 because of Bug 917167. Renominating.
Blocks: 917167
blocking-b2g: koi? → leo?
Comment 12•11 years ago
|
||
Broken (or unreliable) new 1.1 feature (MMS) = blocker.
blocking-b2g: leo? → leo+
Comment 13•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18/rev/60d177e0be64
status-b2g18:
--- → fixed
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → wontfix
status-b2g-v1.1hd:
--- → affected
status-b2g-v1.2:
--- → fixed
status-firefox24:
--- → wontfix
status-firefox25:
--- → wontfix
status-firefox26:
--- → fixed
Target Milestone: --- → 1.1 QE5
Assignee | ||
Comment 15•11 years ago
|
||
Thanks Ryan for the manual merge which looks good to me.
You need to log in
before you can comment on or make changes to this bug.
Description
•