Why your custom keyboard disappears in phone number fields
Tap into the phone number field in Contacts, or a signup form asking for your number, and a third-party keyboard flips back to Apple’s — then returns the moment you tap somewhere else. It is a narrower, less-known cousin of the password-field rule: one specific field type iOS reserves for its own keyboard, and a PIN or price field is not it.
You are typing with a keyboard you actually chose, you tap into a phone number field — adding a contact, a signup form asking for your number — and Apple’s keyboard is suddenly back. Tap into an ordinary text field afterward and yours returns on its own. It reads like a random glitch, especially because it does not happen for every field with digits in it: a PIN box or a price field usually leaves your keyboard alone. The difference is not random. It is one specific field type, and iOS treats it the same deliberate way it treats a password box.
The exact field type this happens to
Apple’s own documentation for building a custom keyboard names it directly: a text field built for a phone number can request one of two related keyboard types, a standard phone pad or the “name and phone pad” that Contacts uses for its phone number row. Apple states plainly that a third-party keyboard is ineligible to type into either one — not a bug, not a missing setting, a restriction written into the field itself.
What actually happens on screen
The instant the cursor lands in one of those two field types, iOS quietly swaps in the system keyboard, exactly the way it does for a password box. Tap into a different, ordinary field afterward and your keyboard resumes there on its own — the rule travels with the field, not with the app, so the same app can hand you back your own keyboard one field later.
Why a PIN, a price or a code is a different case
The fields that trigger the swap are a small, named pair — the phone pad and the name-and-phone pad. A plain numeric field, the kind behind a PIN, a verification code or a price, is usually built from a different keyboard type that is not on that list, so it does not force the swap and your keyboard stays put. What you actually see there is your keyboard’s ordinary layout rather than a stripped-down number pad, because iOS does not automatically simplify a third-party keyboard down to digits only — you reach the numbers the same way you would anywhere else, by tapping into the numbers page. Two fields can both be “just digits” to look at and still behave in opposite ways underneath.
Full Access changes none of it
Same as a password field, this restriction is attached to the field, not to a permission. A keyboard with Full Access on is still ineligible for a phone pad field, and a keyboard with Full Access off is treated no differently there than one with it on — there is no toggle anywhere in Settings that reaches this, because the rule was never about what a keyboard could do with the clipboard or the network. It is about which field is asking.
Where you actually run into it
The Contacts app is the clearest case — add or edit a phone number and the keyboard swaps every time. Plenty of ordinary signup and login forms ask for a phone number the same way, for account verification or two-factor codes, and some delivery or ride-booking apps do too when they collect a contact number. A PIN screen, a one-time code you type in rather than have filled in automatically, and a price or quantity field are the common counterexamples — those usually leave your keyboard exactly where it was.
Where Kibo fits
Kibo runs in phone number fields the same way every third-party keyboard must: it steps aside for the system keyboard there and comes straight back the moment you tap into an ordinary field, because that swap happens at the iOS level and is not something a keyboard app can opt out of. In an ordinary numeric field that is not one of the two restricted types — a PIN, a price, a code — Kibo keeps its usual layout and the same 123 key the rest of this site’s guide on the number row describes, with whichever of its 56 themes and 17 key sounds you have set running the whole time. 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 my custom keyboard turn into Apple’s keyboard in the Contacts app?
The phone number row in Contacts uses a “name and phone pad” keyboard type, one of two field types Apple’s own documentation names as off-limits to third-party keyboards. iOS swaps in its own keyboard there and hands yours back the moment you tap into a different field.
Does this happen for every field with numbers in it, like a PIN or a price?
No. Only the phone pad and name-and-phone pad field types trigger the swap. A PIN, a verification code or a price field is usually built from a different keyboard type, so your keyboard stays — you just reach digits the ordinary way, by tapping into its numbers page, rather than being handed a dedicated number pad.
Will turning on Full Access stop my keyboard from disappearing in phone number fields?
No. The restriction is attached to the field, the same way it is for a password box, so it applies whether Full Access is on or off. There is no setting anywhere that changes it.
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.