Bug 479396 - kdeconnect-sms: conversations list and message lists completely messed up
Summary: kdeconnect-sms: conversations list and message lists completely messed up
Status: RESOLVED WORKSFORME
Alias: None
Product: kdeconnect
Classification: Applications
Component: messaging-application (other bugs)
Version First Reported In: 23.08.4
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Simon Redman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-04 15:26 UTC by Tony Green
Modified: 2024-01-14 02:09 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screenshot showing faulty message list. (186.20 KB, image/jpeg)
2024-01-04 15:26 UTC, Tony Green
Details
Screenshot showing incorrect messages for contact (181.85 KB, image/jpeg)
2024-01-04 15:31 UTC, Tony Green
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tony Green 2024-01-04 15:26:35 UTC
Created attachment 164671 [details]
Screenshot showing faulty message list.

SUMMARY

Rather a vague-looking summary, but the best I can come up with.

Using kdeconnect on my Samsung Android 'phone (app version 1.29, Android version 13) with kdeconnect-sms on my Linux desktop (kdeconnect-sms 23.08-4, Manjaro Linux fully up to date). All necessary permissions have been granted and the requisite SMS plugins are enabled at both ends.

* Conversation list:
1. In general, only single person conversations are listed (so none of those where I've sent SMS messages to multiple contacts). Though ONE multi-person conversation IS listed.
2. Not all conversations shown in my SMS app are shown in the conversations list.
3. A number of long-deleted conversations (no longer shown on the app) are shown.
4. The preview of some conversations shows text from a completely different contact.

* Message list.
Many message lists show only messages from many years ago, with no sign of more recent ones.


STEPS TO REPRODUCE
1. Pair 'phone and desktop
2. Run kdeconnect-sms


OBSERVED RESULT
As described above

EXPECTED RESULT
All messages should be available for all contacts (and groups) and should have correct summaries.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.10-1
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
Comment 1 Tony Green 2024-01-04 15:31:53 UTC
Created attachment 164672 [details]
Screenshot showing incorrect messages for contact

The messages shown for this contact were from a completely different one, which doesn't even appear on the conversations list.
Comment 2 Tony Green 2024-01-04 15:34:04 UTC
Shame I can't edit previous comments. My comment about the summary for contacts being from another contact should say that all messages shown are from a different contact. More info in other comments.
Comment 3 Simon Redman 2024-01-05 21:50:48 UTC
Thanks for taking the time to report this. Unfortunately I can't reproduce what you're experiencing so there isn't much I can directly do.

Did this break recently for you?

What messaging app are you using on your phone?

(In reply to Tony Green from comment #0)
> 1. In general, only single person conversations are listed (so none of those where I've sent SMS messages to multiple contacts). Though ONE multi-person conversation IS listed.

Can you confirm that the messages you've sent to multiple contacts are actually *MMS*? As far as I understand, SMS can only have a single target.

(In reply to Tony Green from comment #0)
> Not all conversations shown in my SMS app are shown in the conversations list.

Can you try to narrow down what is special about all the conversations which are not shown? Are they special messages from your network? Messages from a SIM/phone number which used to be in this phone? Are they from an email address? Etc.

(In reply to Tony Green from comment #0)
> 3. A number of long-deleted conversations (no longer shown on the app) are
> shown.

This sounds like you might have only hidden (archived, etc.) the conversation using your messaging app on Android. Anything like that would be an app-specific setting, so KDE Connect reading messages from the messages databases wouldn't have the information that they should not be displayed.

(In reply to Tony Green from comment #1)
> Created attachment 164672 [details]
> Screenshot showing incorrect messages for contact
> 
> The messages shown for this contact were from a completely different one,
> which doesn't even appear on the conversations list.

This smells like the conversation ID is somehow being corrupted.
Comment 4 Tony Green 2024-01-06 17:58:57 UTC
(In reply to Simon Redman from comment #3)

> Did this break recently for you?

I had actually tried kdeconnect-sms some time ago and abandoned it because of this behaviour. I came back to try it again and decided I'd better report the problem. So the short answer is "no".
> 
> What messaging app are you using on your phone?

The Samsung messaging app. When I tried in the past I was using Textra.
> 
> (In reply to Tony Green from comment #0)
> > 1. In general, only single person conversations are listed (so none of those where I've sent SMS messages to multiple contacts). Though ONE multi-person conversation IS listed.
> 
> Can you confirm that the messages you've sent to multiple contacts are
> actually *MMS*? As far as I understand, SMS can only have a single target.

I think you're right, evidently I may be using incorrect terminology. Though curiously, the *one* multi person conversation that appears on   my desktop has some messages on my 'phone marked MMS and others not.  Though that's a fairly old conversation, not touched since last June.

> 
> (In reply to Tony Green from comment #0)
> > Not all conversations shown in my SMS app are shown in the conversations list.
> 
> Can you try to narrow down what is special about all the conversations which
> are not shown? Are they special messages from your network? Messages from a
> SIM/phone number which used to be in this phone? Are they from an email
> address? Etc.

No pattern I can discern, unfortunately.  I *did* change network a couple of months ago, but given the fact that the previous time I tried it i had the same problem, I'm guessing that's probably irrelevant to this problem.

> 
> (In reply to Tony Green from comment #0)
> > 3. A number of long-deleted conversations (no longer shown on the app) are
> > shown.
> 
> This sounds like you might have only hidden (archived, etc.) the
> conversation using your messaging app on Android. Anything like that would
> be an app-specific setting, so KDE Connect reading messages from the
> messages databases wouldn't have the information that they should not be
> displayed.

I can't see any option to hide messages in the app, so I don't think I've done that.

> 
> (In reply to Tony Green from comment #1)
> > Created attachment 164672 [details]
> > Screenshot showing incorrect messages for contact
> > 
> > The messages shown for this contact were from a completely different one,
> > which doesn't even appear on the conversations list.
> 
> This smells like the conversation ID is somehow being corrupted.

Its feeling like the problem is something screwed up on my 'phone rather than in KDEConnect. So I'm inclined to suggest closing this off and assuming it's a one-off problem at the user-end. Since I can *send* messages from the command line with kdeconnect-cli, I've got most of the functionality I really need anyway. Thanks for your work on this.
Comment 5 Simon Redman 2024-01-14 02:09:40 UTC
(In reply to Tony Green from comment #4)
> Its feeling like the problem is something screwed up on my 'phone rather
> than in KDEConnect.

This is certainly possible. Not a very satisfying outcome, but really the best I can suggest without dissecting your phone on my desk, which I don't have time for and you probably don't want 🙂.

(In reply to Tony Green from comment #4)
> So I'm inclined to suggest closing this off and assuming
> it's a one-off problem at the user-end. Since I can *send* messages from the
> command line with kdeconnect-cli, I've got most of the functionality I
> really need anyway. Thanks for your work on this.

Sounds good. I'm glad you're enjoying it!