SailWarden is an unofficial native Bitwarden client for Sailfish OS. It is currently in beta and requires Sailfish OS 4.5 or greater. This app has near one-to-one feature parity with the official Bitwarden apps. That means most functions you know and love from Android or iOS should be available here with a few exceptions that aren't available on Sailfish, like autofill or syncing with authenticator.
A - Bitwarden is one of the most important applications on my phone and without it, Sailfish could never be the phone I use daily so, I decided to make one. It turned out pretty well so I thought I'd share it with the Sailfish community to help grow the ecosystem. Hopefully somebody finds it useful as well.
A - Well, I know it is because I made it but you should always exercise caution and use your best judgement. A few things you can try to help put your mind at ease:
A - That is completely fair. If you don't feel comfortable using it, don't use it. Thanks to the Android compatibility layer, you can use the official android Bitwarden client.
A -
A - No, the import is strictly additive. It should never delete or modify existing items. Please do backup your secrets before using this feature though because it is new and needs more testing. The official apps require you to do this through the web vault and do not have this functionality in their mobile apps.
A - The one thing I'd like to add is support for multiple accounts but if you have any requests or suggestions use the feedback link in the about section within settings.
SailWarden is an unofficial third-party client and is not affiliated with, endorsed by, or supported by Bitwarden Inc.
| Attachment | Size | Date |
|---|---|---|
| 943.65 KB | 08/07/2026 - 07:40 | |
| 951.26 KB | 08/07/2026 - 07:40 | |
| 982.7 KB | 08/07/2026 - 07:40 |
- 0.1 - Initial Beta Release
- 0.2 - Moved non-sensitive configuration settings (custom server URL, cover layout, and session timeout options) out of the secure OS vault into local settings. Hopefully preventing the app from triggering endless device lock prompts.
- 0.3 Moved more configuration settings and prefetch others to avoid lock prompts.
Comments
explit
Wed, 2026/07/08 - 15:02
Permalink
The app is good, but it doesnt preserve my email address. After locking, i need to enter my email, password and 2FA code again. Another problem: on jolla C2 - there is no fingerprint sensor, bu the app keeps asking for it.
ahjolinna
Mon, 2026/07/06 - 07:22
Permalink
it seems the app freaked out when I hadnt login yet went to multitask view and I got endless SQLCipher plugin spam, the sailfishOS secure storage thing.
aka: /usr/bin/harbour-sailwarden wants to retrive secret: "lastActiveTime", "refreshToken", "reloadToPage", "email", "customServerUrl", & "showCoverDetails" from collection sailwarden in plugin SQLCipher
when it ask all of these things, becomes non-responsive and sailfishOS ask do you want to wait or close the app
I try to run it with GDB but I didnt get any clear errors
FixFlare
Tue, 2026/07/07 - 16:23
Permalink
Hello again,
You've been helpful with providing feedback on multiple apps - I appreciate it. It is folks like you that make me want to release these and not just keep them for myself.
This problem would seem another difference between physical devices and my emulator unfortunately. I've uploaded 0.2 that will hopefully fix that but hard to stay without a real phone with a fingerprint reader I can test with.
I've purposely stripped all debug type logs to try and keep things secure and not leak any sensitive information but I think your description gave me a good idea of where the problem is.
Let me know how it goes.
ahjolinna
Tue, 2026/07/07 - 21:37
Permalink
now it started to ask same thing after I put my email...for "useCustomServer" & "deviceIdentifier"
after the password it asked for these: "kdf", "iterations", "kdfMemory", "kdfParallelism", "masterPasswordHash", "deviceIdentifier", "actualRefreshToken", "publicKey", "folders", "collections".
for some reason it wants to delete them and then store them again...its no wonder it ask them SO MANY times, worst part is that when it ask you get that the app has fozen msg and SailfishOS ask if you want to wait or close the app, so you often click close the app because its its located in the same place as secret thing.... because of this I didnt get all the secrets errors as I rage quited :D
anyway, being a dev and not having a device to test is really a pain would recommend getting one, you could easily buy a cheap 2nd hand device for cheap and flash sailfishOS on it or are you waiting for the Jolla Phone?
FixFlare
Wed, 2026/07/08 - 07:46
Permalink
Yeah, heh - it is one of those things you don't know will be a problem until it is. My dev machine isn't that great and the emulator only has 1GB of RAM so I'm thinking hey, if it works great for me on this slow device it should be no problem for some of these higher end phones with 4GB+ of RAM. Not being able to enable the lock on the emulator makes things difficult for an app like this too.
I ordered a jolla phone but it isn't supposed to arrive until September and that is if they will even ship to the USA. The good news is someone on the sailfish forums was nice enough to offer to send me a device if I pay for shipping so I may take him up on that offer.
Anyways, on to the bug - I was actually able to reproduce that cipher message prompt and the lock this time. I moved some more settings and prefetched others during the login that will hopefully stop too many sync calls from locking up your phone. Since I was able to reproduce it, and now I am not, hopefully that is a good sign that it is fixed now.
Let me know how it goes with 0.3 and feel free to DM if it is easier. Happy to add a credit or something if you want to be a beta tester of sorts.