Does a third-party keyboard work with passkey sign-in on iPhone?
A passkey sign-in never opens a text field at all, so no keyboard shows up during it — not a third-party one, and not Apple’s either. iOS asks Face ID or Touch ID directly, which is a different, more absolute version of what already happens to a custom keyboard in an ordinary password field.
You tap Sign In expecting the usual username and password fields, and instead the whole screen dims and a Face ID prompt slides up with nowhere to type anything — no keyboard, custom or otherwise, in sight. It is a fair thing to notice if you picked a keyboard for its sound or its theme and now cannot tell whether it is even installed correctly. Nothing failed. A passkey sign-in is not a text field with a keyboard hidden somewhere behind it; there is no text field at all.
What a passkey actually replaces
A passkey is a credential built to replace a typed password rather than sit alongside one. Instead of a string of characters you remember and type, the site holds one half of a cryptographic key pair and your iPhone holds the other, generated and stored in the device’s Secure Enclave when you first set the passkey up. Signing in is a matter of proving you hold that half, which iOS does by asking Face ID or Touch ID to unlock it — nothing is typed, because there is nothing to type. It is the same underlying technology behind Apple’s own Sign in with Apple and the passkeys now offered by banks, password managers and a growing number of ordinary login pages.
Why no keyboard appears, not even Apple’s
A keyboard, on iOS, only ever shows up because some text field asked for one. Tap into an empty search bar and a keyboard appears because that field requested it; tap a button instead and nothing does, because a button has no text to receive. A passkey prompt is built the second way. It is a system authentication sheet, the same family of UI as a payment confirmation or a Face ID unlock on the Lock Screen, and it never creates a text field for a username or a password to land in. Asking which keyboard would show up inside it is a bit like asking which keyboard shows up when you unlock the phone itself — the question does not apply, because the mechanism was never built around typing in the first place.
A stricter case than the one password fields already show
A separate guide on this site covers why a custom keyboard steps aside for Apple’s own inside an ordinary password field — that is a privacy rule where iOS reserves a secure text field for the system keyboard specifically, and it is a rule about which keyboard is allowed to appear. A passkey prompt does not need that rule at all, because it removes the entire category the rule was written for. There is no field for either keyboard to compete over, so the outcome is not “Apple’s keyboard instead of yours” — it is no keyboard, for anyone, because none was ever going to be shown.
What happens once Face ID clears
The moment Face ID or Touch ID confirms it is you, the sign-in completes and the app moves straight to whatever comes after login, the same as if a password had been typed and accepted. If that next screen has an ordinary text field in it — a search bar, a message compose box — your usual keyboard appears there exactly as it does anywhere else in that app. The passkey step itself is simply a gap with nothing typed in it, not a stretch of the app where your keyboard is disabled.
When a site still shows you a keyboard anyway
Plenty of sites offer a passkey as one option among several rather than the only one, and some show a username field before the Face ID prompt even for a passkey-only account, so the field can confirm which saved passkey to offer. Typing a username in that kind of field works with any keyboard installed, custom ones included, exactly as it would in any other ordinary text field — it is only the credential step itself, the part that used to be a password box, that a passkey removes and replaces with the Face ID sheet.
Where Kibo fits
Kibo works in any ordinary text field an app offers, username boxes and search bars included, with its own themes, sounds and lighting following it in. A passkey prompt gives no app any text field to hand to a keyboard in the first place, so there is nothing for Kibo, or any other keyboard, to appear in during that specific step — the same reason no keyboard is missing anything when you unlock the phone with Face ID. None of this touches Full Access, which Kibo reads only for the Copy word, Copy line and Paste buttons on its toolbar. It is free to download.
Frequently asked questions
Why does no keyboard show up when I sign in with a passkey on iPhone?
Because a passkey sign-in never opens a text field. iOS asks Face ID or Touch ID directly through a system authentication sheet, and a keyboard only ever appears because a text field requested one — this step never creates one, for Apple’s keyboard or any third-party one.
Is this the same rule that hides a custom keyboard in password fields?
Related, but stricter. A password field is a text field that iOS reserves for its own keyboard specifically. A passkey prompt is not a text field at all, so there is no field for either keyboard to be offered in — the whole category the password-field rule was written for is simply absent.
Will my custom keyboard work on the rest of the sign-in screen?
Yes. If a site shows a username field before offering a passkey, any installed keyboard works there normally. It is only the credential step itself — the part a typed password used to fill — that a passkey replaces with a Face ID or Touch ID prompt and no keyboard at all.
Try it on your own keyboard
Kibo is a free custom keyboard for iPhone with real mechanical key sounds, a wardrobe of themes and RGB backlight effects. No account, no ads, and it works with Full Access left off.