Hey folks,
We’ve released Mailspring 1.13.0, which addresses issues with the snap build of 1.12.0. I was able to reproduce the issues reported above, where the snap was able to write your passwords but not read them after a restart, causing it to succeed on the first run and then get into an invalid + broken state after quitting + restarting.
I fixed it by copying snapcraft.yaml configuration from the chromium snap, which I observed was reading / writing from the keychain successfully. They were building libsecret into the snap explicitly, which did the trick for us as well.
If you snap refresh mailspring, you’ll get the new revision which addresses these issues. If your Mailspring install is broken, you’ll launch into a bit of a mess and I’m really sorry for the hassle. You’ll need to:
-
Go to Preferences > Subscription and sign in to your Mailspring identity again to enable read receipts, send later, etc. (If you were signed in previously).
-
Go to Preferences > Accounts and click “Reconnect” or “Re-authorize” for each account that is shown in red or having connection difficulty.
Thankfully, with this upgrade Mailspring is running on Electron 22 and the new safeStorage APIs, which gives us a clear path forward and makes it much easier to incorporate upstream security patches and updates. I appreciate everyone’s patience and I’m sorry this has been a rocky update.