App Store 4.4.1 rejection: Keyboard extensions

By The Draftbit team · Updated
Sources checked

This guide is for iPhone and iPad apps providing custom keyboard extensions.

Your keyboard has to remain a usable keyboard even when someone declines broader access. Guideline 4.4.1 requires typing functionality, a way to switch to the next keyboard, and operation without full network or full-access permission.

Test with the restrictive settings first

Enable the keyboard with full access disabled and try it without a network. Can users type and move to another keyboard? We’d start there before testing optional online features.

Check what activity is collected. Apple limits collection to improving the keyboard’s function on the device. Keyboards containing stickers or emoji also need to meet the applicable sticker rules.

Remove unrelated actions

Keep keyboard buttons serving their expected input roles. The extension can’t launch other apps except Settings or repurpose a key into an unrelated action, such as opening a camera.

Test ordinary typing, switching keyboards, denied access, and the corrected data behavior in the final build. Tell Apple how to enable the keyboard and which behavior changed. Make the listing match its actual capabilities.

Messages this guide can help with

App Store 4.4.1 rejection; app store 4.4.1 denial; Guideline 4.4.1; Keyboard extensions

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit your iPhone or iPad app for review