Messages imported via SwiftBackup show import date instead of received date

[TalkyPup]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.2.0

Affected Android/Custom ROM version

Android 15 / LineageOS 22.2

Affected device model

Google Pixel 7 Pro

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

1. Use an external app (SwiftBackup in my case, but I imagine the issue could exist with other backup apps too) to restore a backup of SMS messages from a previous installation of Android from either the same device or a different one. (I don't think the messaging app used in the previous installation makes a difference.)
2. Install and run Fossify Messages and set it as the default SMS messaging app.

Expected behavior

All conversations should appear in the order of most to least recent messages.

Actual behavior

All imported messages show the date/time of import instead of the date/time of the last message received. When opening a conversation, the dates and times for individual messages are correct, but the date/time for the conversation on the home screen is not. No other SMS app that I've tried does this. Newer messages received after the import show the correct date/time.

Screenshots/Screen recordings

Incorrect date on home screen:

Correct date on message:

Additional information

I'm not sure if this technically counts as a bug or not. Sorry if it's in the wrong category. I'm also aware that this might seem like I'm reporting a SwiftBackup issue rather than a Fossify one, but Fossify Messages is the only messaging app I've tried that behaves in this way, which is a shame, because it's my preferred SMS app otherwise.

[naveensingh]

Previously reported in #42 (comment).

[TalkyPup]

Sorry I missed that one before posting. I didn't notice that GitHub defaulted to only searching for open issues.

[naveensingh]

It's fine. I commented because there's useful discussion in that thread that would help solve this issue.