Introduction
When Lastpass first came on the scene I jumped on it because of how easy it makes
syncing passwords between devices. Previously, I was using a local password manager
that was only on my computer. Thankfully, mobile logins weren’t nearly as necessary
for daily life back then. However, I still needed my computer to log into anything on
my phone.
Over the years, Lastpass started having security incidents.
This isn’t surprising with how big it became. However, at a certain point I switched
to bitwarden because after LogMeIn, Inc (now GoTo) purchased them, the number of incidents started
accelerating.
Yeah. Bitwarden developed a new android client written by Kotlin to replace old C# client. This new client is in beta testing currently. The old client supports both PascalCase and camelCase but the new client only supports camelCase. And Vaultwarden use PascalCase now, so it’s incompatible with new Android client.
Hope this Pull Request could be merged soon so I can use it with new Bitwarden native Android client.
https://github.com/dani-garcia/vaultwarden/pull/4386
Is this a new breakage? I’ve been using vaultwarden + android for years now?
Yeah. Bitwarden developed a new android client written by Kotlin to replace old C# client. This new client is in beta testing currently. The old client supports both PascalCase and camelCase but the new client only supports camelCase. And Vaultwarden use PascalCase now, so it’s incompatible with new Android client.
Yeah, I looked into that, but I seem to be in the google play beta for bitwarden and nothing is broken? Looks like this is a different beta? Bizarre.
They doesn’t use normal beta channel, and publish a new application named Bitwarden Beta.
https://play.google.com/store/apps/details?id=com.x8bit.bitwarden.beta
This was just merged.