Encode Keyboard Not Showing? 7 Checks for iPhone and iPad

Start with the least disruptive checks. Most cases are resolved before the last step.

• →Open Encode Keyboard and confirm the app launches on iOS 18 or later.
• →Open Settings → General → Keyboard → Keyboards and confirm Encode Keyboard is listed.
• →Open Notes, tap a normal text field, then touch and hold the globe key and select Encode Keyboard.
• →Make sure you are not testing in a password or other secure field.
• →Make sure the field is not using a phone-pad keyboard, such as a phone-number input.
• →Try another app: the current app may intentionally reject third-party keyboards.
• →As a last step, remove Encode Keyboard from the iOS keyboard list, add it again, and retest in Notes.

Apple documents two automatic fallbacks: secure text fields and fields configured for phone-pad input. In both cases iOS temporarily shows the system keyboard. The third-party keyboard should be available again in a normal field.

Apps can also reject every custom keyboard through an application policy. A banking app, enterprise app, or privacy-sensitive workflow may do this. If Encode Keyboard works in Notes, its installation is valid and the specific app or field is the likely boundary.

Convert needs a current line before the cursor and valid input for the selected codec. Put the cursor at the end of a non-empty line and verify the direction and codec.

Some transformations intentionally reject invalid input. For example, Base64 Decode expects canonical Base64 that becomes valid UTF-8 text, while Morse rejects unknown signal groups. Change the codec or correct the input instead of repeatedly tapping Convert.

If the issue remains in Notes, email support with your device model, iOS version, Encode Keyboard version, selected codec, and the step that fails. A screenshot without private text is useful.

Never send passwords, one-time codes, recovery phrases, or other sensitive content. The support team does not need your actual message to diagnose keyboard setup.