Closed
Bug 879152
Opened 13 years ago
Closed 13 years ago
B2G MMS: Set the delivery status to error when retrieveMMS fail.
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
People
(Reporter: ctai, Assigned: ctai)
References
Details
Attachments
(1 file, 2 obsolete files)
|
2.18 KB,
patch
|
airpingu
:
review+
|
Details | Diff | Splinter Review |
We need to set the delivery status to error when retrieveMMS fail. It will cause we can't manually retrieve in second time.
| Assignee | ||
Comment 1•13 years ago
|
||
Attachment #757836 -
Flags: review?(gene.lian)
| Assignee | ||
Comment 2•13 years ago
|
||
This should be a leo+ bug. It will cause we can't manually retrieve MMS in second time.
blocking-b2g: --- → leo?
Comment 3•13 years ago
|
||
Comment on attachment 757836 [details] [diff] [review]
Patch v1.0
Review of attachment 757836 [details] [diff] [review]:
-----------------------------------------------------------------
::: dom/mobilemessage/src/ril/MmsService.js
@@ +1525,5 @@
> // For X-Mms-Report-Allowed
> let wish = aMessageRecord.headers["x-mms-delivery-report"];
> let responseNotify = function responseNotify(mmsStatus, retrievedMsg) {
> // If the mmsStatus is still MMS_PDU_STATUS_DEFERRED after retry,
> // we should not store it into database.
// If the mmsStatus is still MMS_PDU_STATUS_DEFERRED after retry,
// we should not store it into database and update its delivery
// status to 'error'.
@@ +1529,5 @@
> // we should not store it into database.
> if (MMS.MMS_PDU_STATUS_RETRIEVED !== mmsStatus) {
> if (DEBUG) debug("RetrieveMessage fail after retry.");
> aRequest.notifyGetMessageFailed(Ci.nsIMobileMessageCallback.INTERNAL_ERROR);
> + // Retrieved fail after retry, so we update the delivery status in DB.
We don't need this comment and please merge into the above-mentioned.
@@ +1534,5 @@
> + gMobileMessageDatabaseService.setMessageDelivery(aMessageId,
> + null,
> + null,
> + DELIVERY_STATUS_ERROR,
> + null);
This is good but not right. Please put aRequest.notifyGetMessageFailed(...) in the callback of .setMessageDelivery(...).
Attachment #757836 -
Flags: review?(gene.lian) → review-
| Assignee | ||
Comment 4•13 years ago
|
||
Attachment #757836 -
Attachment is obsolete: true
| Assignee | ||
Comment 5•13 years ago
|
||
Attachment #757858 -
Attachment is obsolete: true
| Assignee | ||
Updated•13 years ago
|
Attachment #757860 -
Flags: review?(gene.lian)
Updated•13 years ago
|
Attachment #757860 -
Flags: review?(gene.lian) → review+
| Assignee | ||
Updated•13 years ago
|
Keywords: checkin-needed
Comment 6•13 years ago
|
||
Keywords: checkin-needed
Comment 7•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla24
Updated•13 years ago
|
blocking-b2g: leo? → leo+
Comment 8•13 years ago
|
||
status-b2g18:
--- → fixed
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → wontfix
status-b2g-v1.1hd:
--- → affected
status-firefox22:
--- → wontfix
status-firefox23:
--- → wontfix
status-firefox24:
--- → fixed
Comment 9•13 years ago
|
||
Updated•13 years ago
|
Flags: in-moztrap-
You need to log in
before you can comment on or make changes to this bug.
Description
•