You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting up a new account the sync password is not saved in the Windows Credential Store. This means the user needs to reauthenticate after closing and re-opening the sync client.
I suspect this has something to do with the recent upgrade of Qt/QtKeychain, maybe a wrong build option or something like that. I don't think that it has something to do with the QtKeychain 0.9.1 release in general (see #569), as I can confirm that 0.9.1 itself is clean (I compiled a testclient against 0.9.1 and it is working properly).
I could look into this a bit deeper, but I don't have access to the exact build environment bootstrapping mechanism. I am sure you manage the environment dependencies through a platform management tool (Ansible/Chef/Puppet or whatever), would you mind sharing the environment recipe so people can reproduce the environment for debugging?
Steps to reproduce:
Quit Nextcloud, remove current config and sync folder
Remove all Nextcloud credentials from the Windows Credential Manager
Open Nextcloud client (daily build) and set up account
Quit Nextcloud client
Re-open Nextcloud client → password is lost
The text was updated successfully, but these errors were encountered:
When setting up a new account the sync password is not saved in the Windows Credential Store. This means the user needs to reauthenticate after closing and re-opening the sync client.
I suspect this has something to do with the recent upgrade of Qt/QtKeychain, maybe a wrong build option or something like that. I don't think that it has something to do with the QtKeychain 0.9.1 release in general (see #569), as I can confirm that 0.9.1 itself is clean (I compiled a testclient against 0.9.1 and it is working properly).
I could look into this a bit deeper, but I don't have access to the exact build environment bootstrapping mechanism. I am sure you manage the environment dependencies through a platform management tool (Ansible/Chef/Puppet or whatever), would you mind sharing the environment recipe so people can reproduce the environment for debugging?
Steps to reproduce:
The text was updated successfully, but these errors were encountered: