Bug 492351

Summary:	Cannot add trusted networks in v1.32.1 (F-Droid version)
Product:	[Applications] kdeconnect	Reporter:	Mace <mace68>
Component:	android-application	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED FIXED
Severity:	normal	CC:	alphanine, andrew.g.r.holmes, balbodom, contact+bugs+kde, justin, lantw44, lunatikovv, m-kdeorg, mace68, marco.antonucci75
Priority:	NOR	Keywords:	regression
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Android
OS:	Android 14.x
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Mace 2024-08-29 06:31:32 UTC

SUMMARY

STEPS TO REPRODUCE
1. Open KDE Connect.
2. Access the Trusted networks interface via any method (from settings, etc.).
3. un-check "Allow all" (there is already a (default?) entry of #_# in the list).
4. Tap the Add "<currently-connected-ssid>" button.

OBSERVED RESULT
The currently connected SSID is added to the list successfully but it will not save. Upon returning to the Trusted networks interface the list is empty again, except for that #_# entry. That one can be removed from the list while in the Trusted networks interface, but the removal doesn't persist. The #_# entry returns, by itself, upon returning to the Trusted networks interface.

EXPECTED RESULT
The changes made in the Trusted networks interface should save upon exiting and remain until they're changed again.

SOFTWARE/OS VERSIONS
KDE Connect 1.32.1 (F-Droid)
Android version: 14
Phone model: SM-S928U (Samsung Galaxy S24 Ultra)

ADDITIONAL INFORMATION
All permissions except for Microphone are granted (Location permission is set to "while using the app")

Comment 1 Justin Zobel 2024-08-30 01:50:52 UTC

I've just tested on 1.32.0 from the Google Play store and this doesn't happen for me, are you able to downgrade on F-Droid to see if it occurs on 1.32.0, that way we will know if it's a regression in that newer release, thank you!

Comment 2 Mace 2024-08-30 02:51:10 UTC

Seems 1.32.0 works as it should with Trusted networks.

Comment 3 Justin Zobel 2024-08-30 08:24:36 UTC

Thanks for testing that, I'll set it back to reported to see if anyone can replicate your findings and add the regression tag.

Comment 4 Mace 2024-08-30 10:09:29 UTC

You're welcome. Also, there's an nearly identical report at https://bugs.kde.org/show_bug.cgi?id=492302

Comment 5 alphanine 2024-09-02 16:27:12 UTC

I had the same issue. Downgrading to version 1.32.0 via F-Droid fixed it for me.
I even tried deleting all of the app storage (1.32.1) and setting it up afresh, and it still gave me the same "#_#" networks.

Comment 6 Marco Antonucci 2024-09-07 19:37:42 UTC

Same here after updating to version 1.32.2 from Google Play Store. The only way to get KDE Connect to establish a connection with my PC (Kubuntu 20.04) is by enabling 'Allow all'.

Comment 7 balbodom 2024-09-20 01:18:22 UTC

I have the same issue. I'm on 1.32.2 from F-Droid, running GrapheneOS). Can't save the trusted network. Reverting to 1.32.0 on F-Droid solved the issue.

Comment 8 Albert Vaca Cintora 2024-09-28 16:06:45 UTC

This was fixed in https://invent.kde.org/network/kdeconnect-android/-/merge_requests/472

I'll release a new version.