Nextcloud Desktop Flatpak autostart always asks for new password/logon

I am using Nexctloud Desktop installed via Flatpak on Fedora/KDE, currently in Version

Nextcloud Desktop-Client Version 4.0.6daily (KDE)

When put to KDE autostart on Logon, it will start, but it will always ask for new user logon and start the browser to obtain a new token.

After closing the App and restarting it via KDEs autostart- settings for testing, it will open and have the tokens loaded the right way. No browser will open and the user will be logged in, syncing all files as defined.

Why is it always asking for the new Login/Token at Autostart? Is there any way to fix this, any working Version?

First of all, I think you should try replacing Flatpak with rpm. Less trouble and faster :slight_smile: Uninstall the flatpak-nextcloud and then

sudo dnf install nextcloud-client

If it still doesn’t work, consider to install gnome-keyring to store the password. I don’t know if it is necessary on kde, but it helped me by cosmic. Do this by

sudo dnf install gnome-keyring

When keyring asks for a password, leave it blank, so nextcloud can fetch the password.

Thx for the suggestion. I know that rpm- Version has less probs. But i need Flatpak, while this is not a single pc, but for a bunch of clients, where the rpm is way too old due to the slow rolling distro. As they are managed centrally, i need flatpak version to work everywhere the same.

I already solved it this way: After installation, the flatpacks app- folder is removed completely and after that, we are using autoprovisioning for the first setup.

At least now, the client is not asking for new registration at next startup.

Autoprovisioning has other bugs - so i cannot add a second synced folder when the first provision was done.

I guess thers some glitch in adding the profile the first time in what was bundled with flatpack, which is why even adding the folder manually after installation it does not work there.

Think i open a bug report to find out what going on there.

So removing the app folder and then reconfiguring it, solves the problem for me now.