Duplicate outgoing SMS/MMS entries created in Telephony provider

[samchencode]

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

GrapheneOS (Android 14)

Affected device model

Google Pixel 4a (5G)

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

1. Set Fossify Messages as the default SMS application.
2. Open any conversation.
3. Send an SMS (also reproducible with MMS).
4. Observe the conversation after the message is sent.

Expected behavior

One outgoing message should be created and displayed.

Actual behavior

Two outgoing messages are created for every message sent.

The recipient receives only one SMS/MMS, but two sent messages appear in the conversation. The duplicates are also visible in other SMS applications (including the stock/AOSP Messages app), indicating that duplicate records are being written to Android's Telephony provider rather than being a Fossify UI issue.

Screenshots/Screen recordings

Additional information

• Reproducible every time.
• Happens with both SMS and MMS.
• Clearing app cache does not help.
• Disabling delivery reports does not help.
• Stock/AOSP Messages does not reproduce the issue.
• Fossify Messages is the only default SMS application.
• Other SMS apps display the same duplicate entries because they exist in the system SMS database.

ADB query after sending a single SMS with body "Fossifytest":

adb shell content query --uri content://sms/sent --projection _id,date,date_sent,type,status,sub_id,creator,address,body | grep Fossifytest

Row: 0 _id=3300, date=1781227818202, date_sent=0, type=2, status=-1, sub_id=2, creator=org.fossify.messages, address=REDACTED, body=Fossifytest

Row: 1 _id=3299, date=1781227817753, date_sent=0, type=2, status=-1, sub_id=2, creator=org.fossify.messages, address=REDACTED, body=Fossifytest

Both rows:

• have different _id values
• have different timestamps (~449 ms apart)
• have identical body, address, status, type, creator, and sub_id values
• were created by org.fossify.messages

This appears to be a duplicate insertion into the SMS provider rather than a display issue.