Hubert Lu[:hlu] <hlu@mozilla.com> Reporter
	Description • 11 years ago

Messages, SMS and MMS, are missing when device updates from v1.2 to v1.3 

* Build Info (Both Gecko and Gaia)
     Device    Helix
     Gaia      539a25e1887b902b8b25038c547048e691bd97f6
     Gecko     http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/e672faf1e6a1
     BuildID   20140111004004
     Version   26.0
     ro.build.version.incremental=eng.wanglei.20131212.005845
     ro.build.date=Thu Dec 12 00:58:58 CST 2013


* Reproduce Steps
  1. Flash Helix device to v1.2 build from PVT
  2. Change update URL to v1.3 (http://update.boot2gecko.org/helix/1.3.0/nightly/update_20140111004005.xml)
  3. Send and receive some SMS/MMS
  4. Perform check now to get the update notification.
  5. Download the update package
  6. Install the upgrade package while the package is downloaded.
  
* Actual results:
     Messages, SMS and MMS, are missing when device updates from v1.2 to v1.3 

* Expected results:
     All of messages should be kept.

	Julien Wajsberg [:julienw]
	Comment 1 • 11 years ago

Thanks Hubert, that's what I saw in my early test as well!

	Julien Wajsberg [:julienw]
	Comment 2 • 11 years ago

NI Alexandre who experienced the bug yesterday and managed to still do the upgrade. Will probably have more informations ;)

	:gerard-majax [PTO 01/08/2023-10/09/2023]
	Comment 3 • 11 years ago

In my case, only one MMS was failing.

The first issue triggered was a DataCloneError at http://hg.mozilla.org/mozilla-central/annotate/12d3ba62a599/dom/mobilemessage/src/gonk/MobileMessageDB.jsm#l900

I have no idea what can trigger this issue, but I do have kept the database to reproduce it.

	Gene Lian (I already quit Mozilla)
	Comment 4 • 11 years ago

Hi Bevis, would you mind taking this one?

	Julien Wajsberg [:julienw]
	Comment 5 • 11 years ago

Just to let you know that the reference workload light does not reproduce this bug.

For information, the reference workloads use the format of Firefox OS v1.1, so the issue is probably due to something we added in 1.2.

	:gerard-majax [PTO 01/08/2023-10/09/2023]
	Comment 6 • 11 years ago

In the dump I performed yesterday of the failing MMS, there was a timestamp field: "timestamp":1371915877215.
That is Sat, 22 Jun 2013 15:44:37 GMT. So the build I was running was probably of june, 17th. And branch master.

	Bevis Tseng[:bevis][:btseng](Exited) Assignee
	Comment 7 • 11 years ago

I am taking it and will try to see if I can repo this locally.

	Gene Lian (I already quit Mozilla)
	Comment 8 • 11 years ago

Thanks Bevis! Really appreciate.

	Bevis Tseng[:bevis][:btseng](Exited) Assignee
	Comment 11 • 11 years ago

Root cause found.
1. The DB VERSION mapping in v1.2 and v1.3 is mismatch.
2. VERSION 12 in v1.2 mapped to VERSION 13 in v1.3 which means the logic of VERSION 12 in v.13 was skipped in v1.2.
3. This cause a reference to the null property of messageRecord.deliveryInfo while upgradeSchema14() in MobileMessageDatabaseService.js

Solution will be ready after more testing.