[BUG] Doesn't auto-import messages in chronological order

[jayb-g]

When running it the first time after installation(and after making it default SMS app), it automatically starts loading the messages but all the messages show the same timestamp of when it was imported(and not that of when the message was sent or received). Although when opened, it shows correct time.

So messages order in my stock SMS app and in Simple SMS are completely different.

I also tried to manually export messages from the default SMS app so that I can import it in simple SMS but that also fails since probably the format(keys) don't match. Can you refer to some app that exports SMS in a compatible format? I tried using SMS Import Export

[jondo]

Hmm, this doesn't always happen: I have just installed the current version 5.19.3 on a Pixel phone with Android 13. The auto-import worked correctly.

[jayb-g]

Yes, you might be right. But in my case it is happening again and again. I have tried wiping all the messages and deleting cache for simple SMS app and then reimport messages to default app then again installing the simple SMS app but result is same.

Upon wiping and reimporting to default app, it shows correct order and timestamps. So when simple SMS imports messages from default SMS app, it should load in correct order with all timestamps but that doesn't happen.

So what I want to try is export SMSs to json first, then make it compatible with the schema supported by simple SMS app and then try importing from within simple SMS manually from settings. But I don't know what schema is being used by simple SMS. Maybe someone can point out in the docs or something since its open source.

[jayb-g]

Anyone can point out to the schema used by simple SMS import/export?

So it would be easier to create something that can be used by the community (temporarily until issue is looked into and fixed by devs,)which exports/converts exported jsons to the schema supported and importable by simple SMS.

[jayb-g]

@jondo I'm on Android 14. Can that be a problem ?

I now see that #783 and #499 may be related to this issue