Bug 415531

Summary: KDE Connect mistakenly thinks a conversation is a group if the latest message was a received RCS message
Product: [Applications] kdeconnect Reporter: Simon Redman <simon>
Component: android-applicationAssignee: Simon Redman <simon>
Status: REOPENED ---    
Severity: normal CC: anthonyryan1, gomanab
Priority: NOR    
Version First Reported In: 1.10   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Simon Redman 2019-12-24 16:56:20 UTC 
SUMMARY
KDE Connect mistakenly thinks a conversation is a group if the latest message was a received RCS message

STEPS TO REPRODUCE
0. Enable RCS
1. Convince someone else to enable RCS
2. Convince that person to send you a message
3. Launch KDE Connect SMS app

OBSERVED RESULT
KDE Connect SMS app reports the conversation is a group conversation (two targets, each is the actual other party)

EXPECTED RESULT
KDE Connect SMS app reports the conversation is a single-target conversation

SOFTWARE/OS VERSIONS
KDE Connect release version 1.4 / Android version 1.10

ADDITIONAL INFORMATION
I believe this is an issue which can be fixed on the Android side only, so it should not require a desktop app release version upgrade.
Comment 1 Simon Redman 2020-01-18 02:03:46 UTC 
On pondering, I'm pretty sure this should be resolved in the Android app by checking for duplicate addresses when collecting those for the conversation
Comment 2 Simon Redman 2023-01-22 15:25:35 UTC 
This has been resolved; probably by exactly the thought I had earlier of enabling Android to strip out the user's own phone number.
Comment 3 gomanab 2024-05-24 22:11:03 UTC 
How do you enable android from stripping out your number in the message? I am having this same issue.
Comment 4 Simon Redman 2024-05-24 22:51:37 UTC 
(In reply to gomanab from comment #3)
> How do you enable android from stripping out your number in the message? I
> am having this same issue.

There is no configuration option, though I agree that this issue has reoccurred. I don't know why the fix worked for a bit and then did not.