I suppose, it’s because of this:
[W] unknown:0 - "Collection bitsailor in plugin org.sailfishos.secrets.plugin.encryptedstorage.sqlcipher is owned by a different application"
In the past, this could be resolved by removing the collection from /home/defaultuser/.local/share/system/privileged/Secrets/org.sailfishos.secrets.plugin.encryptedstorage.sqlcipher, but not any more.
i tried the API login too but i also get a “incorrect credentials”. Did you succeed with the bitwarden cli ?
Well, I got it to work again. What I did, was to clean up all installations of bitwarden-cli (there were more than 1, as I fiddled around with it a couple days ago):
devel-su npm uninstall @bitwarden/cli -g
Omit the “-g” flag, if you have an instance installed underneath “defaultuser”. Doesn’t hurt to run the command with and without the -g flag.
Then, I went ahead and installed it again:
devel-su npm install @bitwarden/cli -g
Just to be sure, I linked the “bw” binary from bitwarden-cli to the locations /usr/bin and /usr/local/bin again:
ln -sf /usr/local/bin/node-22.3.0/bin/bw /usr/bin/bw
ln -sf /usr/local/bin/node-22.3.0/bin/bw /usr/local/bin/bw
Afterwards, I was able to log back in using API credentials. It’s all working again. I hope, it’ll stay this way. 
BitSailor had trouble in showing the correct OTP codes here. Xperia 10 III SFOS 4.6.0.15
At first, I wasn’t able to install the app because of npm and node.js are too old for installing bitwarden-cli. Now it works but if I select a TOTP Code the numbers did not refresh and at the most websites the codes did not work. It seems that there is a huge delay in receiving the TOTP code from the servers.
Can anyone confirm that issue?
You don’t receive TOTP codes from servers, part of TOTP is that it gets it’s uniqueness from the current time, but it gets calculated locally on your device.
If most of your TOTP codes don’t work, it’s very likely that your device date or clock is skewed.
Date and time, looking good. So the time step value seems not be the issue. I will check this too, if the C2 arrived here. Did anyone use TOTP with BitSailor?
And sorry for the misleading “code from server”.
Have you checked with other clients/webinterface if codes from those match codes generated by BitSailor? Could also be caused by something being wrong with the TOPT secret or settings.
I can’t replicate this on my Xperia 10 III, the codes work.
I also cannot replicate the node.js issues, I’ve got a fresh install of SailfishOS, simply installed BitSailor, went through the setup and all seems to work well.
I found out what seems to be the problem with the TOTP codes, as I faced it too. Indeed it was about the secret. BitSailor only generates a correct code if just the secret is stored in the field. As an example the entry for my Google account, for which the generated verification code works:
████████████████████████████████
And for my Z account, for which BitSailor doesn’t give a correct verification code:
otpauth://totp/Z:█████████████████████?secret=████████████████████████████████&issuer=Z
It can be fixed on the user side @playforvoices by checking your non-working entries and removing that part before and after the secret.
On the developer side @Rikudou_Sennin the problem could be avoided by implementing a parser for otpauth:// URIs, maybe similar to the Android client.
The only case that remains are Steam Guard codes, as they use a different format and are represented in Bitwarden by steam:// followed by the secret. @Rikudou_Sennin you could maybe look at SailOTP or Foil Auth for their implementation, if you plan to have them properly generate in BitSailor.
Thanks for the info! I’ll check it out.
@sourcrowd @avhakola I’ve released an update which correctly parses the TOTP url (thanks again @sourcrowd!).