MMS not imported/exported correctly

[Throun]

When importing my messages on an old phone, none of the MMS imported appear correctly. The SMS apps I tested show that a message exists, from the correct contact and sent or received at the correct time. However, the message itself does not appear.

The app does show that MMS is being backed up when exporting and importing. Regular SMS messages from the same backups don't seem to be affected.

[tmo1]

• Did you by any chance turn off "Include (encoded) binary MMS data ..." when exporting?
• Inspect the JSON - do you see the missing message data there?
• What versions of SMS I/E and Android were used when exporting and importing?

[Throun]

• No, it's enabled, that's one of the things I checked first.
• I can't check every message, but the ones I checked did have their message data present in the JSON.
• I am using version 1.5.1 from F-Droid on both devices. As for Android, OneUI 3.1 (Android 11) on my regular phone and AOSiP 10 (Android 10) on the importing phone.

[tmo1]

Okay - I've never seen or heard of something like this. Would you please post some JSON that demonstrates the problem, as per the guidelines here?

[Throun]

messages-redacted-2022-12-07.json.txt

Ok, here's the JSON, saved as a text file.

[tmo1]

Thank you. I'm working on this - I'll report any progress.

[tmo1]

The problem was the presence of tags named sef_type in the MMS parts. These are not present in the Android Telephony.MMS.Part table, and they therefore caused the part inserts to fail. I have no idea what these tags are - perhaps they were introduced by one of the messaging apps (QKSMS or Simple Mobile Tools: Simple SMS Messenger) used on the source system?

In any event, the solution was to add a routine to drop all tags not present in the destination MMS part table (something we previously had to do for the basic SMS and MMS tables).

[Throun]

Sorry for bumping this, but would it be possible to make a new release to get this fix?

[tmo1]

Done.