SUMMARY i updated to the 1.33.0 android version of kdeconnect and the phone is not discoverable and cant discover my fedora workstation 41 nor windows 10 machine. i am using the f-droid version. i downgraded to 1.32.11 and it works there STEPS TO REPRODUCE 1. try connecting paired or unpaired device OBSERVED RESULT cant connect to fedora worksatation 41 nor windows 10 EXPECTED RESULT connect to my devices SOFTWARE/OS VERSIONS Windows: 10 Linux: Fedora Workstation 41 Android: Android 14 OneUi 6
Same here, using Ubuntu 24.10 android 12 and the android version 1.33.0 doesn't work. Downgrading fixes the issue
Same here KDE Connect app version 1.32.11 from F-droid. With: SOFTWARE/OS VERSIONS Linux (Debian 13 - unstable repository) / KDE Plasma: KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.12.17-amd64 (64-bit) Mesa Version: 25.0.0-1 Graphics Platform: Wayland HARDWARE SPECIFICATIONS Hardware: Laptop Dell Inspiron 5770 (17" 1080p@60Hz screen) CPU: Intel® Core™ i5-8250U CPU @ 1.60GHz GPU 1: Intel® UHD Graphics 620 (main, Vulkan capable) GPU 2: AMD Radeon R5 M465 Series RAM: 8 GiB (7.7 GiB usable) There's also the Neguard application firewall on the phone and OpenSnitch application firewall on computer, but at least it should say where it got stuck. as the necessary firewall rules have been made for both. Adding the computer by ip says that it could ping it, but that's about all.
Could it be an ssl cert or ssl lib issue on the android app? I geta tons of these in my logs (gsconnect): (translate to TLS connection with the pair server failed: the TLS connection was not closed properly) ``` mars 04 20:48:53 hermes gjs[2832687]: JS ERROR: Gio.TlsError: La négociation TLS avec le serveur pair a échoué : La connexion TLS n’a pas été terminée correctement. _promisify/proto[asyncFunc]/</<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:453:45 _init/GLib.MainLoop.prototype.runAsync/</<@resource:///org/gnome/gjs/modules/core/overrides/GLib.js:263:34 ### Promise created here: ### _authenticate@file:///home/prahal/.local/share/gnome-shell/extensions/gsconnect@andyholmes.github.io/service/backends/lan.js:606:26 _encryptServer@file:///home/prahal/.local/share/gnome-shell/extensions/gsconnect@andyholmes.github.io/service/backends/lan.js:700:21 open@file:///home/prahal/.local/share/gnome-shell/extensions/gsconnect@andyholmes.github.io/service/backends/lan.js:756:43 async*_onIdentity@file:///home/prahal/.local/share/gnome-shell/extensions/gsconnect@andyholmes.github.io/service/backends/lan.js:396:27 async*_onIncomingIdentity@file:///home/prahal/.local/share/gnome-shell/extensions/gsconnect@andyholmes.github.io/service/backends/lan.js:352:18 _init/GLib.MainLoop.prototype.runAsync/</<@resource:///org/gnome/gjs/modules/core/overrides/GLib.js:263:34 ```
I just pushed KDE Connect v1.33.1 which should fix this issue, indeed the problem was with the device ID validation being too strict. Sorry for the inconvenience 🙇
(In reply to Albert Vaca Cintora from comment #4) > I just pushed KDE Connect v1.33.1 which should fix this issue, indeed the > problem was with the device ID validation being too strict. Sorry for the > inconvenience 🙇 thanks for the fix dude, I really appreciate it. For now, I'll keep using the 1.32.11 and wait till 1.33.1 version appear in droid-ify or play store
I wonder if you should not revert to your initial regex after next GSConnect release with their device ID fix up code, which won't use hyphens anymore. Your call. Just wanted to note that allowing hyphens only fix newer GSConnect installs as my old install GSConnect device ID was my hostname it seems so still not working with 1.33.1 device ID regex. The only way out seems to be to install GSConnect nightly, but for now I have been unable to get this nightly to work.