Stuck on "Searching for devices..." even though identity packets are recieved #2139
Description
Describe the bug
I'm trying to pair my devices again after a recent update to the KDE Connect Android app resulted in them not being able to find each other, and now I'm getting really weird behavior. Desktop side, I see that the identity packet is received, however neither device shows the other as being available for pairing (it doesn't show up at all).
Steps to reproduce
Normal pairing steps
Expected behavior
They devices should "see" each other and show up in one of the devices list.
GSConnect version
71
Installed from
GNOME Extensions website
GNOME Shell version
49.4
Linux distribution/release
Fedora Linux 43 (Workstation Edition)
Paired device(s)
Pixel 10
KDE Connect app version
1.35.3
Plugin(s)
No response
Support log
Feb 16 21:08:52 org.gnome.Shell.Extensions.GSConnect[99309]: [service/backends/lan.js:broadcast:438]: "Broadcasting to LAN"
Feb 16 21:08:56 org.gnome.Shell.Extensions.GSConnect[99309]: [service/backends/lan.js:_onIdentity:377]: {
"id": 1771297737221,
"type": "kdeconnect.identity",
"body": {
"deviceId": "a7d0e4a55c9f43168e7a9b54107520fb",
"deviceName": "xxxxx xx",
"protocolVersion": 8,
"deviceType": "phone",
"incomingCapabilities": [
"kdeconnect.battery",
"kdeconnect.clipboard",
"kdeconnect.clipboard.connect",
"kdeconnect.contacts.request_all_uids_timestamps",
"kdeconnect.contacts.request_vcards_by_uid",
"kdeconnect.findmyphone.request",
"kdeconnect.mousepad.keyboardstate",
"kdeconnect.mousepad.request",
"kdeconnect.mpris",
"kdeconnect.mpris.request",
"kdeconnect.notification.request",
"kdeconnect.notification.reply",
"kdeconnect.notification.action",
"kdeconnect.ping",
"kdeconnect.notification",
"kdeconnect.runcommand",
"kdeconnect.sftp.request",
"kdeconnect.share.request",
"kdeconnect.share.request.update",
"kdeconnect.sms.request",
"kdeconnect.sms.request_conversations",
"kdeconnect.sms.request_conversation",
"kdeconnect.sms.request_attachment",
"kdeconnect.systemvolume",
"kdeconnect.telephony.request_mute"
],
"outgoingCapabilities": [
"kdeconnect.battery",
"kdeconnect.clipboard",
"kdeconnect.clipboard.connect",
"kdeconnect.connectivity_report",
"kdeconnect.contacts.response_uids_timestamps",
"kdeconnect.contacts.response_vcards",
"kdeconnect.digitizer.session",
"kdeconnect.digitizer",
"kdeconnect.findmyphone.request",
"kdeconnect.mousepad.request",
"kdeconnect.mpris.request",
"kdeconnect.mpris",
"kdeconnect.notification",
"kdeconnect.ping",
"kdeconnect.presenter",
"kdeconnect.notification.request",
"kdeconnect.mousepad.echo",
"kdeconnect.mousepad.keyboardstate",
"kdeconnect.runcommand.request",
"kdeconnect.sftp",
"kdeconnect.share.request",
"kdeconnect.sms.messages",
"kdeconnect.sms.attachment_file",
"kdeconnect.systemvolume.request",
"kdeconnect.telephony"
],
"tcpPort": 1716,
"tcpHost": "xxx.xxx.xxx.xxx
}
}
Feb 16 21:08:56 org.gnome.Shell.Extensions.GSConnect[99309]: [service/backends/lan.js:open:791]: "opening lan://xxx.xxx.xxx.xxx:1716 (69c6357d-c590-4c17-bf27-7b37498713e0)"
Screenshots
No response
Notes
- IP addresses and device names in the logs are redacted for privacy, but the real values are completely fine and valid.
- I'm using some extra debug logging from my fork, see james-pre@58b7386