Why your custom keyboard disappears in password fields
Why iOS swaps your third-party keyboard for the Apple one whenever you tap a password box, why it happens even with Full Access off, and why there is nothing to fix.
You are happily typing with a custom keyboard, you tap into a password box, and the Apple keyboard is suddenly back. The moment you move to the next field, your keyboard returns. Nothing is broken, and you did not switch anything by accident — iOS did it on purpose, and it does it to every third-party keyboard, not just yours.
What is actually happening
An app can mark a text field as a secure field — the kind that hides what you type behind dots. When the cursor lands in one of those, iOS quietly sets that field aside for the system keyboard and takes third-party keyboards out of the running. Your keyboard is not crashing or being blocked by a setting; it is simply not offered for that one field. Leave the field and it comes straight back, because the rule is attached to the field, not to your keyboard.
Why iOS does this
It is a privacy decision. A third-party keyboard, if it has Full Access, is capable of sending what you type off the device. For most typing that trade is yours to make, but a password is the one moment where the cost of a mistake is highest. Rather than trust every keyboard to behave in that moment, iOS removes the possibility entirely and hands the field to its own keyboard, which it controls end to end.
The fields that trigger it are the sensitive ones:
- Password boxes almost everywhere — logins, Wi-Fi passwords, app sign-ins.
- Passcode and PIN entry.
- Many card-number and payment sheets, where the app has marked the field secure.
It is the app that decides which of its fields count as secure, so you will meet it in some places and not others. A search bar never triggers it; a banking login always does.
It happens even with Full Access off
This is the part that surprises people who chose a keyboard specifically because it does not need Full Access. A keyboard with Full Access off has no way to read the clipboard, let alone send your keystrokes anywhere — the permission that would allow it is switched off. But iOS does not weigh that up field by field. Secure field means system keyboard, regardless of what the third-party keyboard can or cannot do. The rule is blunt on purpose: it is easier to trust when it has no exceptions to reason about.
What you can do about it
Nothing, and that is the honest answer. There is no toggle in Settings, no permission to grant, and no keyboard that can opt back in — a keyboard that could override this would defeat the point of it. The good news is that there is nothing to fix, because nothing is wrong. Your keyboard returns the instant you leave the secure field.
If your aim was to avoid typing the password at all, that is a different feature called Password AutoFill, where iOS offers a saved password above the keyboard. It works alongside any keyboard because iOS supplies the password itself rather than letting the keyboard read it — a separate mechanism from the one described here.
Where else the same thing happens
The lock screen behaves in a related way: replying to a notification from the lock screen often uses the Apple keyboard even when you have a custom one set, for much the same protective reasons. So a custom keyboard that seems to “disappear” is usually iOS reserving a sensitive spot for its own keyboard, not a fault in the app you installed.
How this looks with Kibo
Kibo is built to run with Full Access off, and its themes, sounds and lighting come with it into ordinary apps. In a password or payment field it steps aside for the Apple keyboard like every third-party keyboard must — that behaviour is iOS, not something Kibo sets or can change. Kibo reads Full Access in exactly one place, the copy and paste buttons on its toolbar, and a secure field is untouched by that either way.
Frequently asked questions
Is my custom keyboard broken because it vanishes in password fields?
No. iOS reserves secure text fields for the system keyboard and takes every third-party keyboard out of the picture there. Your keyboard returns the moment you tap out of the field. It is expected behaviour, not a fault.
Does turning on Full Access make my keyboard appear in password fields?
No. The rule applies to secure fields regardless of a keyboard’s permissions, so Full Access changes nothing here. iOS hands the field to its own keyboard either way.
Can I force my custom keyboard to work in a password box?
There is no setting for it, and no keyboard can override it — a keyboard that could would defeat the privacy reason the rule exists. If you would rather not type the password, use Password AutoFill, which offers a saved password above whatever keyboard you have.
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.