https://bugs.kde.org/show_bug.cgi?id=425638
--- Comment #18 from Simon Redman <si...@ergotech.com> --- (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) -- You are receiving this mail because: You are watching all bug changes.
