SUMMARY F-Droid is currently in the process of changing the repository URL scheme: https://gitlab.com/fdroid/fdroidclient/-/issues/2390 The KDE F-Droid repository (https://community.kde.org/Android/FDroid) has already made changes to comply with this change, however the URL under which the repository advertises itself is still wrong. This wrong value is in the repo.address field in this JSON: https://cdn.kde.org/android/stable-releases/fdroid/repo/index-v1.json This misconfiguration makes it so the F-Droid repository can be registered in the F-Droid client with the correct URL, but after the first refresh, the client will re-configure the repository to use the obsolete address from the repo.address field. STEPS TO REPRODUCE 1. Newly add the KDE F-Droid repository to the F-Droid client. 2. Tap on the repository entry to see that the URL is correct (ends with "repo/"). 3. Refresh the F-Droid client. 4. Check the repository entry again to see that the URL is now wrong (does not end with "repo/"). ADDITIONAL INFORMATION - The F-Droid team has removed handling for this deprecated scheme in the upcoming 1.16 release of the F-Droid client, meaning the repository will effectively stop working then. In F-Droid 1.16-alpha (or newer), subsequent refreshes will show a toast message indicating that the repository does not work and KDE apps cannot be installed. - I have talked to the F-Droid team about this and the information which field has a wrong value is from them. They would be happy to help with any further questions and can be contacted via https://f-droid.org/about/#contact .
Most likely, we need to update the value of `repo_url` in the `config.yml` of our repo(s). The next run of `fdroid deploy` (which is run by binary factory) should update the advertised URL. See https://f-droid.org/en/docs/Setup_an_F-Droid_App_Repo/#customization.
Should be fixed for both repos. Moreover, they should now have a KDE gear icon (whereever that is displayed).
I can confirm, it's now working for both repos, using F-Droid 1.16-alpha4. I have notified the F-Droid team as well. Thanks for rolling out the fix so quickly!