AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.19.070 Firefox os v1.0.1 Mozilla build ID:20130407070205 +++ This bug was initially created as a clone of Bug #441135 +++ DEFECT DESCRIPTION: (1)There is some old SMS(yesterday for example) from one number, and open the SMS, it will be shown in yesterday zone. (2)Receive a new SMS from the number , and check the list, the thread will be still shown in yesterday zone,And the time is still the time for the old message. but if you open it ,you can see the new message.----NOK1 (3)KIll the message APP, then relaunch it again, that thread will be displayed in today's zone. (4)And open the thread, delete the today's new message. Then go back to the thread list, the message is still displayed in the Today's zone,and the time shown is for the deleted today's message---- NOK2 REPRODUCING PROCEDURES: EXPECTED BEHAVIOUR: NOK1: it should be displayed in today's zone, and with correct time for the latest message NOK2: it should be listed in yesterday area, and with correct time ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: Serious REPRODUCING RATE: 100% For FT PR, Please list reference mobile's behavior: ++++++++++ end of initial bug #441135 description ++++++++++

Please find out which bug regressed this, and when.

I've been checking it and it seems to be a Gecko issue. When deleting a SMS from the SMS-List, Thread-List should be updated as expected. However, even killing the app and opening it again, 'getThreads' returns the 'deleted' message. I've tried with m-c and B2g18 and Im getting same result. Vicamo, could you take a look?

Confirmed.

In bug 833291, saveRecord() did not update threadRecord::lastMessageId. https://mxr.mozilla.org/mozilla-central/source/dom/mobilemessage/src/ril/MobileMessageDatabaseService.js#894

try https://tbpl.mozilla.org/?tree=Try&rev=f53d03f3084e

We've got a patch here acknowledging what we need to fix here, so we no longer need to get a regression window here now.

https://hg.mozilla.org/projects/birch/rev/f48a55068512 https://hg.mozilla.org/projects/birch/rev/5aac2bd2db88

https://hg.mozilla.org/mozilla-central/rev/f48a55068512 https://hg.mozilla.org/mozilla-central/rev/5aac2bd2db88

https://hg.mozilla.org/releases/mozilla-b2g18/rev/e7951efbe489 https://hg.mozilla.org/releases/mozilla-b2g18/rev/88965bc27171 This is going to need a separate b2g18_v1_0_1 patch, unfortunately :(

(In reply to Ryan VanderMeulen [:RyanVM] from comment #11) > This is going to need a separate b2g18_v1_0_1 patch, unfortunately :( Yes, and I'm verifying it. :)

After my verified on our FF version 125. Problems still exist.