Love the new passkeys on iOS, thanks a lot.
A little issue, I’ve got sites with URI matching set as exact host. When choosing Passkeys, Bitwarden display passkeys for all sites with matching base domain, even if the subdomain (ie full host) doesn’t match
How do I sign up for the beta flight for iPad? I’ve downloaded the Test Flight app but I need a Bitwarden beta code.
Click TestFlight link on the main post.
just got the testflight for iOS, but even though I can see passkeys in my vault, when I attempt to use it, iCloud appears to be the one taking over the interaction
tried on both Firefox and Safari
Have u tried refreshing Bitwarden data in the iPad app? This only happened to me twice, one with an unsynchronized iPad client and once with the previous version bug.
Oh and also don’t forget to set the url of that password / account record in Bitwarden.
yeah, i’ve refreshed my vault but the issue still happens.
it’s worth nothing that this is a passkey added to my github username/password combo — i just used it with the firefox extension even
I noticed that it requires connection to the Bitwarden server in order to operate. Not sure if this is intentional or not but you can’t use the passkeys like your offline Bitwarden password vault.
Hi 
I have two questions regarding passkeys on Android:
Thx for sharing some insights 
Hey there. My understanding is that it will use Google Play Services APIs and is only available in Android 14 and above, which opened support for 3rd-party passkeys. If you have additional feedback please add it here - the development team is monitoring!
Thx @RyanL for your reply, really appreciate it 
I’m closely following the growing passkey support of Bitwarden because at the moment, my phone stack does not support this. As I’m very keen to not feeding the big data monopolys like Google, I’m looking for alternatives.
At the moment, I’m using the Android OS called /e/OS (based on LineageOS) which focuses on data privacy. While many basic Android features are part of the open sources Android Open Source Project (AOSP), Google decided some years ago to move some key features into their proprietary Google Play Services (GPS) - things like push notifications, etc.
To bridge this gap, many people use MicroG which is an open source implementation of GPS - so does /e/OS.
When it comes to new features being added to GPS, they have to be reimplemented in microG - of course always a piece of work that a small group of enthusiasts accomplishes in contrast to a big army of Google developers.
When it comes to passkeys, Google went down the same road: many key features of passkeys are implemented in the GPS and are therefore not available to users like me.
So during my search for an alternative implementation of passkeys that does not rely on GPS, I stumbled over Bitwarden and was hoping that you guys will come up with a solution that does not rely on proprietary APIs like GPS and therefore would be a viable alternative.
That’s basically my background, I hope I could shed some light on it?!
Is there a way to install the android beta if I don’t have google play store?
Hard fail on the new native Android app beta
It won’t log in unless you allow it to phone home to beacons5.gvt3.com.
I use Adguard DNS which blocks this, and on log in, the query log shows this domain being blocked.
If I turn off Adguard, I can log in.
Is the iOS testflight version for the native app out?
I can only find the ‘old beta version’ for passkeys available on Testflight.
Edit: It appeard after first leaving and then joining the beta again.
The new mobile app is finally here
…just in time for me to have moved off Bitwarden 
[1]
Personally, even if I was still a fulltime Bitwarden user, I wouldn’t be too excited for the new mobile app update. I do not mean that with any word of disparagement, I assume most of this was trying to get a MVP out without having to continue developing a, shudders, Xamarin app (god I really with MS made that work).
The new app is definitely snappier than the old one (search is still a bit slow), but basic functionality seems to be broken, like TOTP, auto-fill and Face ID unlocking (I am on beta iOS so take that with a grain of salt).
The UI, still has an air of, “this was designed people who are specialists in cryptography not design”, which might be what you want from a password manager, but I will still give my:
Okay, lets look at the old app, the new app, and for comparison, 1Password, which usually gets referred to as the password managers for want good looking apps, which is handy because that’s the one I’m using now-a-days.
You’ll see that when it comes to pure information density, the old BW app is a clear winner, and the 1P app is the clear loser, but, it’s not always that straight cut.
My personal problems with the new design are:
In my opinion, the new design is a downgrade in usability (it’s harder to visually scan), but I’d love to see improvements (even if I’m not there to use them)
specifically, to 1Password, which, in general, I do prefer to BW, but when it comes to UI, BW has the basics in place, but lacks polish, 1P has extreme polish (like you can not only autofill to websites, but native desktop apps too), but has some questionable decisions, like, in the mobile app I can’t see a way to copy a password from the generate password screen, and weaker security for family & org accounts ↩︎
TOTP, autofill, and Face ID work, so it’s probably due to you being on iOS beta.
However, I’m on iOS stable and I’m having issues getting passkeys to work with this Testflight version.
And for the rest of your feedback – spot on!
It feels like they aimed to keep the same “theme” (understandably) while ‘modernizing’ it, inadvertently making everything less dense and less usable, instead of doing a proper rework (naturally subject to change).
I don’t know why but the login won’t work for me (Android beta).
I can type in my mail and the passphrase. The first login seems to work but it wants me to type in the passphrase again. It tells me that it is wrong although I can login with the passphrase on vault.bitwarden.com
I am experiencing the exact same behavior. I wanted to try it but tried multiple times and says username or password incorrect while I am really sure it is correct.
I hope this gets fixed as it is quite basic
Not support Microsoft Authenticator loGin
The release blog post, Bitwarden releases phased beta for native mobile apps | Bitwarden Blog covered this a bit. Passkeys are currently not available in the new apps but the team is hard at work implementing support and it will be available before the general availability of the new apps.
