Closed Bug 879151 Opened 12 years ago Closed 12 years ago

[MMS] Message thread listing turns into empty after sending a MMS

Categories

(Firefox OS Graveyard :: Gaia::SMS, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:leo+)

RESOLVED WORKSFORME
blocking-b2g leo+

People

(Reporter: noemi, Assigned: iliu)

Details

(Whiteboard: QARegressExclude)

Scenario: OS version: 1.1.0.0-prerelease Platform version: 18.0 Build identifier: 20130603100120 Git commit info: cb6d9120b97a50b86da6e5d73d59c84 Device: Unagi After sending a MMS, suddenly, all the threads disappear from the message thread listing. Under this scenario, if you try to send a new MMS to one of the contacts with who you already had a message thread before the issue appearing, the MMS is properly sent and you can see all the previous MMSs sent/received to/from that contact. Tapping on back button shows you again an empty message thread listing window. Please find in the following link a video showing the MMS failing scenario: https://www.dropbox.com/s/8i0z2ut31vndtn5/20130603_185716.mp4 After switching off/on the device all the message threads are available again from messsage thread listing window.
blocking-b2g: --- → leo?
blocking-b2g: leo? → leo+
Assignee: nobody → iliu
I cannot reproduce the issue on build version 20130604230205(b2g18, v1-train). It will need QA's support. Git commit info: ed5cee06576544a99fa5a9612f64ede75b0b6913 Device: Unagi
Keywords: qawanted
I am not able to reproduce it either with Gecko-7c7faef Gaia-b5937ae (v1-train), so definitely some QA assistance is needed here ;-) Thanks!
Whiteboard: QARegressExclude
Noemí, can you confirm this either still exists or has been resolved? Thanks!
Flags: needinfo?(noef)
I'm not able to reproduce it either with the lastest versions: - Gecko-68ad212 Gaia-ea18de8 (v1-train) - Gecko-132c4aa Gaia-ba1cf2a (v1-train) so WORKSFORME?
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(noef)
Resolution: --- → WORKSFORME
Keywords: qawanted
You need to log in before you can comment on or make changes to this bug.