"Invalid file format" when importing call history from simplemobiletools version 5.18.1

[vpelletier]

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.8.0

Affected Android/Custom ROM version

Android 15

Affected device model

Fairphone 6

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

The overall use-case is that of migrating from one android phone to another.

Note: phones used with fr_FR locale and messages back-translated. They should be clear enough, even if approximate.

1. Install simplemobiletools phone app version 5.18.1
2. Cause some call history entries to be created
3. In "Settings", use "Export call history", chose a location, save
4. Copy the call history to a phone with Fossify Phone app version 1.8.0
5. In 3-dots-menu, "Settings", user "Import call history", chose the file, import

Expected behavior

The call history ends up being imported, ignoring any unsupported attribute and picking a default value for any missing attribute.

Actual behavior

A bubble (?) appears at the bottom of the screen with "Importing" caption, then disappears and is replaced with one containing "Invalid file format". The call history is not imported.

Screenshots/Screen recordings

No response

Additional information

I have installed the latest release (1.9.0) and reproduced the issue, but as it is not currently available from F-Droid at the moment I reported this issue against 1.8.0 .

The exported json file can be parsed with python3's (3.13.9) builtin json parser (file opened as utf-8-encoded), so the file seems syntactically clean at a pure json level.

Grepping FossifyOrg/Phone source code with the name of a few properties in the exported file points me to app/src/main/kotlin/org/fossify/phone/models/RecentCall.kt. There are a few apparent differences:

• groupedCalls and simColor are present in the structure, not in the json
• neighbourIDs is present in the json, not in the structure

Also, checking the change history for this file I see startTS was changed from Int to Long, but I guess this is harmless.

I have been unable to locate the source of the Invalid file format error message.

[vpelletier]

Having done a few calls on the fossify version I could export the log, compare the content and replace a few values in the simplemobiletools version so it could be imported.

What I did was:

• remove neighbourIDs
• add simColor with the same value as the one present in the fossify export (not sure if this is required nor how it is used, I know these calls happened on the same SIM so I though I would rather have them be categorized as such)
• add 000 at the end of all startTS, otherwise it would date all imported calls as having happened in 1970.

Also, I took care of removing the trailing newline my text editor added upon saving.