Bug 494030

Summary: KDEConnect Android app constant crashing since update to 1.32.4
Product: [Applications] kdeconnect Reporter: Tony Green <kde>
Component: android-applicationAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andrew.g.r.holmes, me
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Android   
OS: Android 14.x   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Logcat output from adb
Systemd journal filtered on kdeconnect

Description Tony Green 2024-10-03 11:12:02 UTC
Created attachment 174362 [details]
Logcat output from adb

SUMMARY

Since being updated to 1.32.4, the KDEConnect app on my Android 'phone crashes as soon as I open it.
STEPS TO REPRODUCE
1. Tap on KDEConnect icon
OBSERVED RESULT
For about a second, a message flashes up:
"This paired device is not reachable. Make sure it is connected on your same network".

The app then crashes.

EXPECTED RESULT

App should work as before.

SOFTWARE/OS VERSIONS

Android 'phone:
Samsung Galaxy A13
One UI version 6.1
Android 14
Kernel version 4.19.191-28701252-abA137FXXU6EXG3

Desktop machine:
Operating System: Manjaro Linux
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.11.0-6-MANJARO (64-bit)
Graphics Platform: X11
Processors: 4 × AMD Ryzen 3 2200G with Radeon Vega Graphics
Memory: 30.3 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics

(This problem also manifested itself with KDE 6.0.5, before I upgraded my desktop yesterday).
ADDITIONAL INFORMATION

If I clear the app's data and re-start it, it allows me to pair with my desktop (proving it *can* connect to it). But once paired, it crashes. Pair requests seem to work in both directions.
Comment 1 Tony Green 2024-10-03 11:13:06 UTC
Created attachment 174363 [details]
Systemd journal filtered on kdeconnect
Comment 2 Tony Green 2024-10-03 11:18:42 UTC
One additional piece of info. The app has all requested permissions allowed.
Comment 3 Iyán Méndez Veiga 2024-10-03 14:00:47 UTC

*** This bug has been marked as a duplicate of bug 493943 ***