Open bitestring opened 1 year ago
Seconding this, it seems to be due to a change in how VS Code deals with keychains:
NOTE: This section applies to VS Code version 1.80 and higher. In 1.80, we moved away from keytar, due to its archival, in favor of Electron's safeStorage API. -- https://code.visualstudio.com/docs/editor/settings-sync#_troubleshooting-keychain-issues
Same here, is it possible to work around this issue?
Just to confirm here, it's really annoying to sign in every time you restart the IDE.
@mscharley I performed the logging:
[main 2023-08-04T08:05:45.566Z] Going to get password from keytar: vscode.login account
[main 2023-08-04T08:05:45.566Z] Doing get password from keytar: vscode.login account
[main 2023-08-04T08:05:45.566Z] Did not get a password from keytar for account: account
I see even more things, like this
[23:0804/100545.865489:VERBOSE1:os_crypt_linux.cc(207)] Decryption failed
Error: Error while decrypting the ciphertext provided to safeStorage.decryptString.", source: vscode-file://vscode-app/app/extra/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js
It later seems to delete the current key, and generate a new one.
Looks completely broken to me.
See https://github.com/flathub/com.visualstudio.code/issues/415 (possible duplicate)
The following workaround works for me: https://github.com/flathub/com.vscodium.codium/issues/239
However it's not safe, as @Dryadxon already explained. :/
Since the update to VSCode 1.80.x, it can no longer remember credentials for syncing. I have to sign in everytime I open VSCode.
Host: Fedora Worstation 38 Desktop: GNOME 44 VSCode: 1.80.1 (Flathub)