Devices don't see each other after Android app 1.33 update

Help
, ,
1

Hello.
None of my devices see each other since the app was updated in the Play Store to 1.33.0
My list of Devices

  • Intel i3-2100 running Ubuntu 22.04 (Gsconnect installed from the repos)
  • Samsung Galaxy Tab S 8.4
  • Samsung Galaxy S5 Mini (old phone used as a music player)
  • Samsung Galaxy Note9

I think it’s not a firewall issue since Syncthing and Warpinator works.

Neither of these devices see each other, and I can’t downgrade the app on the mobile devices due to installed from the play store.

Any help? Or will be fixed in next update?

2 Likes
2

Same with fdroid version, as well. Both 1.32 are ok, and both 1.33 do not work.

GSconnect as well. Could be GSconnect issue, not KDE connect android app.

3

Same issue here. Up to this version my PC, mobile and tablet could connect. As of 1.33.0 that’s no longer the case.

4

I’m also experiencing this issue following Play store updates to 1.33.0. Devices are Samsung Galaxy S23 Ultra and Tab S8+.

5

It’s not a GSConnect issue. Forgot to mention but I have another, older tablet (Samsung Galaxy Tab 3 7.0) where I’ve have an older version of KDE Connect app (1.21.0) installed manually from FDroid, and it immediately connected to my PC, but not the other devices.

1 Like
6

I see, old versions do work. I mean it could be, that new version do not works only with GSConnect in Gnome, but works with KDE Connect in KDE.

7

Version 1.33.1 dropped in the play store.

The connectivity issue is fixed on all my deviced. Thank you!

8

Oof. I’ve typed that comment too early.
Connecting to the PC does work, but the mobile devices still can’t see each other :frowning:

That was a feature I’ve made use of since that’s how I exchanged clipboard and files between devices.

9

I can confirm that this is a regression in 1.33 update.

To confirm this, I downgraded kdeconnect on Android by following these steps:

  1. In F-Droid, I disabled updates for KDEConnect (!!! Note: This is dangerous. In case you are doing the same, please remember to enable updates again once this regression is fixed!!!)
  2. In F-Droid, I uninstalled KDEConnect (1.33.0)
  3. In F-Droid, I installed KDEConnect 1.32.11 via the “Versions” section at the screen’s bottom
  4. I paired the device again

With this, it works again :slight_smile:
So it seems like this can be used as a workaround until the bug has been fixed.

The bug tracker also has a few reports for this problem. It seems like the devoper(s) are aware of the problem and have suggested that 1.33.1 should fix it: https://bugs.kde.org/show_bug.cgi?id=501043

10

The 1.33.1 update fixes the issues for me too :slight_smile: