Add Error Handling for keytarSet and keytarGet

[hellodword]

Have you read a contributing guide?

• [X] I have read CONTRIBUTING.md
• [X] I have searched the existing issues and didn't find any that were similar
• [X] I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

On Linux, anytype uses keytar/libsecret to call org.freedesktop.secrets dbus for reading and storing the mnemonic.

However, as far as I can see, there is no error handling in the code when calling WalletCreate and WalletRecover directly.

This might be the cause of this issue.

Expected Behavior

I am not sure whether we should prevent users from creating keys and entering Space if org.freedesktop.secrets dbus is unavailable, but I think there should at least be a notification.

Steps To Reproduce

1. Remove or disable services like gnome-keyring on your computer, or ensure they require a password to use.

2. Open anytype and create a key.

3. You will proceed to the next step without any error notification, but the mnemonic will not be displayed, and it will not be saved successfully. Upon exiting, you will be unable to re-enter the wallet and will need to create it again.

Environment

- OS: NixOS
- Version: 0.41.1

Anything else?

No response

[hellodword]

I think we should consider about finding an alternative to the keytar package, as it is no longer maintained.

How about using the safeStorage from Electron?

I noticed that VSCode has moved from keytar to safeStorage: https://code.visualstudio.com/docs/editor/settings-sync#_troubleshooting-keychain-issues

• https://freek.dev/2103-replacing-keytar-with-electrons-safestorage-in-ray
• https://github.com/microsoft/vscode/issues/185677

The benefits I can identify are:

1. All the advantages of getting rid of an unmaintained dependency.
2. It will make package maintainers happier, for instance: https://github.com/squalus/anytype-flake/blob/181bd21e80edcb6c6c72b814ab7ba082baee0ccd/anytype/default.nix#L70-L74
3. Easier cross-platform and architecture support.

@ra3orblade

[hellodword]

While developing anytype-ts in a devcontainer, it's difficult to get org.freebsd.secrets functioning properly. The safeStorage feature provides plaintext storage if no secret store is available.

if (!developerMode && !safeStorage.isEncryptionAvailable()) {
    // warn and exit
}

[ra3orblade]

I think we should consider about finding an alternative to the keytar package, as it is no longer maintained.

How about using the safeStorage from Electron?

I noticed that VSCode has moved from keytar to safeStorage: https://code.visualstudio.com/docs/editor/settings-sync#_troubleshooting-keychain-issues

• https://freek.dev/2103-replacing-keytar-with-electrons-safestorage-in-ray
• Move off of Keytar microsoft/vscode#185677

The benefits I can identify are:

1. All the advantages of getting rid of an unmaintained dependency.
2. It will make package maintainers happier, for instance: https://github.com/squalus/anytype-flake/blob/181bd21e80edcb6c6c72b814ab7ba082baee0ccd/anytype/default.nix#L70-L74
3. Easier cross-platform and architecture support.

@ra3orblade

Last time I've checked safeStorage in some article it described it as not so safe compared to keytar, but maybe something changed in latest versions. I think we can switch to it eventually, but need to understand how to properly migrate so users won't need to enter their phrase manually.

[ra3orblade]

Thanks for links, I'll add the issue to the Linear.