Hi Alekksander,

Sorry you're having this trouble

Can you please check to make sure the SMS plugin is enabled on your phone and the desktop? Do you see the messaging history when you load the app the first time?

Can you attach a file with the logcat output right after you attempt to send a message?

Thanks,
Simon

Hi,

I can confirm this bug on several computers (but one phone, though it happens both with stock ROM and flashed LineageOS). Contrary to OP, the SMS app works intermittently (and unpredictably).

SMS plugin is enabled everywhere and I can see the message history just fine (even when the SMS fails to send SMS, it can update the history just fine). How exactly can I produce a log?

I forgot to add: using up-to-date openSUSE Tumbleweed and KDE Connect 20.08.0. But I have been experiencing this bug for a while (months) now.

Simon Redman thank You for the interest. Yes messaging history loads okay. Terminal doesn't say anything when i press „send”, but here is what it says on entering app and loading a thread:

qrc:/qml/ConversationList.qml:74: TypeError: Cannot read property 'text' of null
qrc:/qml/ConversationList.qml:65: TypeError: Cannot read property 'text' of null
qrc:/qml/ConversationList.qml:74: TypeError: Cannot read property 'text' of null
qrc:/qml/ConversationList.qml:65: TypeError: Cannot read property 'text' of null
QGridLayoutEngine::addItem: Cell (0, 0) already taken
QGridLayoutEngine::addItem: Cell (0, 1) already taken
QGridLayoutEngine::addItem: Cell (0, 0) already taken
QGridLayoutEngine::addItem: Cell (0, 1) already taken
QGridLayoutEngine::addItem: Cell (0, 0) already taken
QGridLayoutEngine::addItem: Cell (0, 1) already taken
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet: Theme.View instead
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet: Theme.View instead
qrc:/qml/ConversationDisplay.qml:211:17: QML TextArea: Binding loop detected for property "implicitHeight"
qrc:/qml/ConversationDisplay.qml:211:17: QML TextArea: Possible anchor loop detected on fill.
qrc:/qml/ConversationDisplay.qml:211:17: QML TextArea: Possible anchor loop detected on fill.
qrc:/qml/ConversationDisplay.qml:211:17: QML TextArea: Possible anchor loop detected on fill.
qrc:/qml/ConversationDisplay.qml:211:17: QML TextArea: Binding loop detected for property "topInset"
qrc:/qml/ConversationDisplay.qml:211:17: QML TextArea: Possible anchor loop detected on fill.
qrc:/qml/ConversationDisplay.qml:211:17: QML TextArea: Binding loop detected for property "topInset"
qrc:/qml/ConversationDisplay.qml:211:17: QML TextArea: Binding loop detected for property "topInset"
qrc:/qml/ConversationDisplay.qml:211:17: QML TextArea: Possible anchor loop detected on fill.
qrc:/qml/ConversationDisplay.qml:211:17: QML TextArea: Possible anchor loop detected on fill.

(In reply to alekksander from comment #0)
> SUMMARY
> Composed SMS messages are not being send, but disappear instead when
> pressing „paper plane” button (or enter). New received messages are
> displayed properly. Also replying to messages from notification „reply”
> works okay.
> 
> STEPS TO REPRODUCE
> 1. Open KDE Connect SMS
> 2. Go to any thread
> 3. Reply any input and send
> 
> OBSERVED RESULT
> Composed text disappears from composing area, but isn't send.
> 
> EXPECTED RESULT
> Text is being send properly.
> 
> SOFTWARE/OS VERSIONS
> Linux/KDE Plasma: KDE neon 5.19 User Edition
> KDE Plasma Version: 5.19.4
> KDE Frameworks Version: 5.73.0
> Qt Version: 5.14.2

I have been having this same problem, I can reply but only on the notification. When I open up the "KDE Connect SMS" all my text are there and it gives me the option to compose but when I hit 'enter' or I click the airplane my message disappears and nothing gets sent.

correction:
„qrc:/qml/ConversationDisplay.qml:211:17” starts on keyboard input.

I am also having this issue, this time on an ASUS ZenFone 6 with stock Android. I note additionally that using kdeconnect-cli doesn't work:

```
[curtispf@curtis-desktop ~]$ kdeconnect-cli -n 'ASUS_I01WD' --destination '[telephone number redacted for privacy]' --send-sms "Test SMS message"
error: No such method 'sendSms' in interface 'org.kde.kdeconnect.device.sms' at object path '/modules/kdeconnect/devices/64c999b24315dfe1/sms' (signature 'ss')
```

I can see all of my messages, but cannot reply to any of them - they simply disappear.

(In reply to Curtis Parfitt-Ford from comment #7)
> [curtispf@curtis-desktop ~]$ kdeconnect-cli -n 'ASUS_I01WD' --destination
> '[telephone number redacted for privacy]' --send-sms "Test SMS message"
> error: No such method 'sendSms' in interface 'org.kde.kdeconnect.device.sms'
> at object path '/modules/kdeconnect/devices/64c999b24315dfe1/sms' (signature
> 'ss')
> ```

The particular issue you've mentioned with the CLI is different than the first issue described here, and is described in this bug report: https://bugs.kde.org/show_bug.cgi?id=425731

Does anyone here notice if you have a mis-matched SMS app and daemon version? Probably your package manager can tell you what version you have installed or it's in the about screen of the SMS app. If there are mis-matched package versions, the SMS app will not work (exactly in the way you're describing) since this is not a scenario I expected to support.

Sorry, I just noticed there was a question above about how to get the `adb logcat` output. Please set up ADB (likely your package manager has a package to install this, please look up how to set up ADB for your distro)

Please try to send an SMS, then run this command:
`adb logcat org.kde.kdeconnect:I *:S > kdeconnect-logcat.txt`

Then attach the kdeconnect-logcat.txt file to this bug report -- I don't think I log anything sensitive, but please take a quick look through the log to make sure.

kdeconnect-cli -n 'AGM A9 Ru' --destination '[phone number]' --send-sms "Test SMS message"
error: No such method 'sendSms' in interface 'org.kde.kdeconnect.device.sms' at object path '/modules/kdeconnect/devices/a6d298bf4c71bb3a/sms' (signature 'ss')

with „adb logcat org.kde.kdeconnect:I *:S > kdeconnect-logcat.txt” the log shows nothing on above command. also nothing when trying to send with gui.

dpkg -s shows:
Package: kdeconnect
Status: install ok installed
Priority: optional
Section: kde
Installed-Size: 5576
Maintainer: Neon CI <neon@kde.org>
Architecture: amd64
Version: 20.08.1-0xneon+20.04+focal+build7
Replaces: kdeconnect-common (<< 20.04.3)
Depends: kde-cli-tools, libqca-qt5-2-plugins, plasma-framework, qml-module-org-kde-kirigami2, qml-module-org-kde-people, qml-module-qtquick-controls, qml-module-qtquick-controls2, qml-module-qtquick-layouts, qml-module-qtquick2, sshfs, libc6 (>= 2.14), libfakekey0 (>= 0.1), libkf5configcore5, libkf5configwidgets5, libkf5coreaddons5, libkf5dbusaddons5, libkf5i18n5, libkf5iconthemes5, libkf5kcmutils5, libkf5kiocore5, libkf5kiofilewidgets5, libkf5kiowidgets5, libkf5notifications5, libkf5people5, libkf5pulseaudioqt2 (>= 1.2), libkf5service5, libkf5solid5, libkf5waylandclient5, libkf5widgetsaddons5, libqca-qt5-2 (>= 2.3.1), libqt5core5a (>= 5.14.2+dfsg), libqt5dbus5 (>= 5.14.2+dfsg), libqt5gui5 (>= 5.14.2+dfsg), libqt5multimedia5, libqt5network5 (>= 5.14.2+dfsg), libqt5qml5 (>= 5.14.2), libqt5quick5 (>= 5.14.2), libqt5widgets5 (>= 5.14.2+dfsg), libqt5x11extras5, libstdc++6 (>= 5.2), libx11-6, libxtst6
Suggests: python-nautilus
Breaks: kdeconnect-common (<< 20.04.3)
Conffiles:
 /etc/xdg/autostart/org.kde.kdeconnect.daemon.desktop 1e7e0c15dfae182b61e706ac88a398e4
Description: connect smartphones to your KDE Plasma Workspace
 Tool to integrate the KDE Plasma Workspace with your smartphones and
 similar devices.
 It adds a set of plasmoid, plugins and services to the KDE Plasma Workspace.
 At the  moment it only supports Android based devices.
Homepage: https://kdeconnect.kde.org

Having the same issue with samsung galaxy note 9 but my messages never go through.

I am also experiencing this bug.  I can say that I have successfully sent a few sms messages, but it rarely works.  I compiled and installed kdeconnect-kde from source in hopes of fixing it and it hasn't worked at all since then.

    kdeconnect-sms -v
    kdeconnect.sms 21.03.70

I installed adb in hopes of helping.  I try to send an SMS (disappears like usual) and then run 

    adb logcat org.kde.kdeconnect:I *:S >> ~/kdeconnect-logcat.txt

I get

- waiting for device -

I ctrl-C to quit and kdeconnect-logcat.txt is empty

There is no change if I reverse the order (running adb logcat first and then trying to send and SMS).  I still have to ctrl-C out of adb and the log is still empty.

I am running Debian testing w/ Plasma

More than happy to contribute (almost) any info needed - just ask!

(In reply to pyr0m4n14c12 from comment #12)
> I am also experiencing this bug.  I can say that I have successfully sent a
> few sms messages, but it rarely works.  I compiled and installed
> kdeconnect-kde from source in hopes of fixing it and it hasn't worked at all
> since then.
> 
>     kdeconnect-sms -v
>     kdeconnect.sms 21.03.70
> 
> I installed adb in hopes of helping.  I try to send an SMS (disappears like
> usual) and then run 
> 
>     adb logcat org.kde.kdeconnect:I *:S >> ~/kdeconnect-logcat.txt
> 
> I get
> 
> - waiting for device -
> 
> I ctrl-C to quit and kdeconnect-logcat.txt is empty
> 
> There is no change if I reverse the order (running adb logcat first and then
> trying to send and SMS).  I still have to ctrl-C out of adb and the log is
> still empty.
> 
> I am running Debian testing w/ Plasma
> 
> More than happy to contribute (almost) any info needed - just ask!

I want to add that I just realized my 'send' airplane is greyed out.  I've been hitting 'enter' to send so I never noticed.  I can browse files on my phone from my PC and I can send pings.  Kde Connect shows them as successfully paired.

I know this is an older bug, but I can confirm that it's still present on 21.12.3. If I click reply from the notification popup, my text goes through. If I try to send a text from the KDE Connect SMS app, it disappears and nothing is sent.

I'm running Linux Mint 21 and using a Samsung Galaxy S22. I will also note that I have a physical AND eSIM on my phone. I'm not sure if that fact may be contributing to this bug.

Somehow I am still missing email notifications on this bug... Here's a mega reply.

Firstly, to everyone, does this happen the first time you launch kdeconnect-sms, or only after awhile? (Specifically, after the phone has lost connection)

(In reply to pyr0m4n14c12 from comment #12)
> I installed adb in hopes of helping.  I try to send an SMS (disappears like
> usual) and then run 
> 
>     adb logcat org.kde.kdeconnect:I *:S >> ~/kdeconnect-logcat.txt
> 
> I get
> 
> - waiting for device -

This looks like you haven't paired your adb devices. Make sure you've accepted the debugging fingerprint on the phone, and that `adb devices` shows you have one device paired.

(In reply to pyr0m4n14c12 from comment #13)
> I want to add that I just realized my 'send' airplane is greyed out.  I've
> been hitting 'enter' to send so I never noticed.  I can browse files on my
> phone from my PC and I can send pings.  Kde Connect shows them as
> successfully paired.
This is probably unrelated. It's more likely you're seeing https://bugs.kde.org/show_bug.cgi?id=455149


(In reply to Nathan from comment #14)
> I know this is an older bug, but I can confirm that it's still present on
> 21.12.3. If I click reply from the notification popup, my text goes through.
> If I try to send a text from the KDE Connect SMS app, it disappears and
> nothing is sent.
> 
> I'm running Linux Mint 21 and using a Samsung Galaxy S22. I will also note
> that I have a physical AND eSIM on my phone. I'm not sure if that fact may
> be contributing to this bug.

KDE Connect SMS worked with dual-sim setups. I no longer have a dual SIM setup to test. Also there's always the chance that Samsung has broken something on their end.

Can you get a logcat, as described above?

> (In reply to Nathan from comment #14)
> > I know this is an older bug, but I can confirm that it's still present on
> > 21.12.3. If I click reply from the notification popup, my text goes through.
> > If I try to send a text from the KDE Connect SMS app, it disappears and
> > nothing is sent.
> > 
> > I'm running Linux Mint 21 and using a Samsung Galaxy S22. I will also note
> > that I have a physical AND eSIM on my phone. I'm not sure if that fact may
> > be contributing to this bug.
> 
> KDE Connect SMS worked with dual-sim setups. I no longer have a dual SIM
> setup to test. Also there's always the chance that Samsung has broken
> something on their end.
> 
> Can you get a logcat, as described above?

I've installed adb and can confirm that my computer sees my device.

:$ adb devices
List of devices attached
R5CT10HN9MP	device

I've tried both, running "adb logcat org.kde.kdeconnect:I *:S > kdeconnect-logcat.txt" before and after trying to send an SMS message from my PC, but in both cases, it just sits there waiting and the file is empty. I sent a reply from the notification while the logcat was running, but nothing populate the file then either.

I can read SMS but I stopped being able to send them when I updated From LineageOS 19 to 20 (Android 12L to 13) on my bramble. Here's what logcat continuously states when I try to send.

12-31 22:12:07.148 15551 15972 E TelephonyHelper: at org.kde.kdeconnect.Backends.LanBackend.LanLink$$ExternalSyntheticLambda0.run(Unknown Source:4) 
12-31 22:12:07.188 15551 15972 E Sending message: java.lang.IllegalArgumentException: org.kde.kdeconnect_tp: Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent. 
12-31 22:12:07.188 15551 15972 E Sending message: at org.kde.kdeconnect.Plugins.SMSPlugin.SmsMmsUtils.sendMessage(SmsMmsUtils.java:188) 
12-31 22:12:07.188 15551 15972 E Sending message: at org.kde.kdeconnect.Plugins.SMSPlugin.SMSPlugin.onPacketReceived(SMSPlugin.java:414) 
12-31 22:12:07.188 15551 15972 E Sending message: at org.kde.kdeconnect.Device.onPacketReceived(Device.java:570) 
12-31 22:12:07.188 15551 15972 E Sending message: at org.kde.kdeconnect.Backends.BaseLink.packageReceived(BaseLink.java:70) 
12-31 22:12:07.188 15551 15972 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.LanLink.receivedNetworkPacket(LanLink.java:250) 12-31 22:12:07.188 15551 15972 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.LanLink.lambda$reset$0(LanLink.java:98) 
12-31 22:12:07.188 15551 15972 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.LanLink.$r8$lambda$XXXXXXXXXXXXXXXXX(Unknown Source:0)
12-31 22:12:07.188 15551 15972 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.LanLink$$ExternalSyntheticLambda0.run(Unknown Source:4)

(In reply to bb81710y from comment #17)
> I can read SMS but I stopped being able to send them when I updated From
> LineageOS 19 to 20 (Android 12L to 13) on my bramble. Here's what logcat
> continuously states when I try to send.
> 
> 12-31 22:12:07.148 15551 15972 E TelephonyHelper: at
> org.kde.kdeconnect.Backends.LanBackend.LanLink$$ExternalSyntheticLambda0.
> run(Unknown Source:4) 
> 12-31 22:12:07.188 15551 15972 E Sending message:
> java.lang.IllegalArgumentException: org.kde.kdeconnect_tp: Targeting S+
> (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE
> be specified when creating a PendingIntent. 
> 12-31 22:12:07.188 15551 15972 E Sending message: at
> org.kde.kdeconnect.Plugins.SMSPlugin.SmsMmsUtils.sendMessage(SmsMmsUtils.
> java:188) 
> 12-31 22:12:07.188 15551 15972 E Sending message: at
> org.kde.kdeconnect.Plugins.SMSPlugin.SMSPlugin.onPacketReceived(SMSPlugin.
> java:414) 
> 12-31 22:12:07.188 15551 15972 E Sending message: at
> org.kde.kdeconnect.Device.onPacketReceived(Device.java:570) 
> 12-31 22:12:07.188 15551 15972 E Sending message: at
> org.kde.kdeconnect.Backends.BaseLink.packageReceived(BaseLink.java:70) 
> 12-31 22:12:07.188 15551 15972 E Sending message: at
> org.kde.kdeconnect.Backends.LanBackend.LanLink.receivedNetworkPacket(LanLink.
> java:250) 12-31 22:12:07.188 15551 15972 E Sending message: at
> org.kde.kdeconnect.Backends.LanBackend.LanLink.lambda$reset$0(LanLink.java:
> 98) 
> 12-31 22:12:07.188 15551 15972 E Sending message: at
> org.kde.kdeconnect.Backends.LanBackend.LanLink.
> $r8$lambda$XXXXXXXXXXXXXXXXX(Unknown Source:0)
> 12-31 22:12:07.188 15551 15972 E Sending message: at
> org.kde.kdeconnect.Backends.LanBackend.LanLink$$ExternalSyntheticLambda0.
> run(Unknown Source:4)

This crash looks like a new issue (specifically because it says "version 31 and above")
Albert had to bump the SDK version for the Google Play release. By any chance did you notice if you got the new KDE Connect app over the weekend, and was that correlated to the new errors you get? (Or did you update your phone over this weekend as well, so it's hard to say?)

Could you open a new bug for this issue, please? I'll try to make time for it this week since from my quick research it should be straightforward and probably broken for everyone.

(Relevant commit: https://invent.kde.org/network/kdeconnect-android/-/commit/6fbd923c60538c2cc6da22246f5b523ef3160256)

Created a bug for the specific issue reported by bb81710y@spymail.one which is due to the SDK bump https://bugs.kde.org/show_bug.cgi?id=464392. If you're experiencing that (as I said before, I imagine everyone is experiencing it) please watch there.

Fairphone 4 KDE connect version 1.21.1

Kubuntu 22.10 KDE connect Version 22.08.3-0ubuntu1~ubuntu22.10~ppa1

I started experiencing this issue only after a fairly recent update to the Kubuntu KDE connect app.  Previously I was able to send SMS flawlessly.
I also lost the ability to "reply" to any notifications at all which also used to work for those applications where it was offered i.e. Email, Signal, Telegram etc.
This may, of course, have to be the subject of another report.

(In reply to James Pirie from comment #20)
> Fairphone 4 KDE connect version 1.21.1
>
> Kubuntu 22.10 KDE connect Version 22.08.3-0ubuntu1~ubuntu22.10~ppa1
>
> I started experiencing this issue only after a fairly recent update to the
> Kubuntu KDE connect app.  Previously I was able to send SMS flawlessly.

1.21.1 was the last version which had the SDK version bug. 1.22+ contain the fix. Are you sill seeing issues with SMS?

(In reply to James Pirie from comment #20)

> I also lost the ability to "reply" to any notifications at all which also
> used to work for those applications where it was offered i.e. Email, Signal,
> Telegram etc.
> This may, of course, have to be the subject of another report.

Replying to notifications is a totally different "pipeline" than SMS. Did you file a bug for this?

(In reply to Nathan from comment #16)
> > (In reply to Nathan from comment #14)
> > > I know this is an older bug, but I can confirm that it's still present on
> > > 21.12.3. If I click reply from the notification popup, my text goes through.
> > > If I try to send a text from the KDE Connect SMS app, it disappears and
> > > nothing is sent.
> > > 
> > > I'm running Linux Mint 21 and using a Samsung Galaxy S22. I will also note
> > > that I have a physical AND eSIM on my phone. I'm not sure if that fact may
> > > be contributing to this bug.
> > 
> > KDE Connect SMS worked with dual-sim setups. I no longer have a dual SIM
> > setup to test. Also there's always the chance that Samsung has broken
> > something on their end.
> > 
> > Can you get a logcat, as described above?
> 
> I've installed adb and can confirm that my computer sees my device.
> 
> :$ adb devices
> List of devices attached
> R5CT10HN9MP	device
> 
> I've tried both, running "adb logcat org.kde.kdeconnect:I *:S >
> kdeconnect-logcat.txt" before and after trying to send an SMS message from
> my PC, but in both cases, it just sits there waiting and the file is empty.
> I sent a reply from the notification while the logcat was running, but
> nothing populate the file then either.

That is odd. If you're still up for it, could I trouble you try running
"adb logcat" or "adb shell logcat" alone, and see if that shows anything
at all? You should get a very large output. Don't attach the output here,
mind, as it'll likely have sensitive information from other apps on the
phone.

Hi Simon,

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!