Closed Bug 853752 Opened 7 years ago Closed 7 years ago
B2G MMS: after retrieving MMS, delete the thread containing the previous notification indication
When receiving an MMS, we expect to receive 2 types of notification indications. The first one is asking users to retrieve MMS. The second one is the retrieved MMS with the real content and receivers. For now, we're treating these 2 notification indication as 2 different DB records. However, we shouldn't do that because they should belong to different threads. A user scenario could be: one thread collects the "download request" messages and the other collects the real MMS message involved with the receivers. See bug 845643 for the previous implementation.
After some off-line discussions, we decide to change our goal for this issue to: after retrieving MMS (that is, a retrieval confirmation is received), we should delete the thread containing the previous notification indication, if the thread doesn't contain any messages anymore.
Summary: B2G MMS: shouldn't treat the two notification indications as different DB records when receiving MMS → B2G MMS: after retrieving MMS, delete the thread containing the previous notification indication
Assignee: nobody → ctai
Status: NEW → ASSIGNED
Gene want to take this bug. Change to him.
This should also be marked as leo+, because we should delete the notification thread after the MMS is received. Otherwise, we'll have redundant threads referring to the same MMS.
blocking-b2g: --- → leo?
This looks like a leo+ to me.
Attachment #739097 - Flags: review?(vyang) → review+
I'll land this after some testings.
Since the Madrid work week is finished, I'm not very sure we should land this patch to inbound or birch. Ask for checkin-needed. Try server looks fine.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
https://hg.mozilla.org/releases/mozilla-b2g18/rev/dcdc2b74cff1 Per the conclusion during the work week in Madrid, we were in agreement we could land the MMS patches to the b2g18 branch. This patch doesn't touch the RIL interface change so it should be pretty safe to land.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Attachment #741791 - Flags: review?(vyang) → review+
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.