App Store 4.4 rejection: App extensions
By The Draftbit team · Updated
Sources checked
This guide is for iPhone and iPad apps including extensions such as keyboards, Safari tools, or other system integrations.
The main app may pass your checks while an extension creates the rejection. Guideline 4.4 requires extensions to follow the relevant Apple programming guidance, be accurately described, and avoid marketing, advertising, or in-app purchases inside the extension.
Test the extension where people use it
Enable it through the appropriate system setup and use it outside the main app. Check its screens, links, and shared libraries. We’d inspect each build target separately; a component included for the main app can also be bundled into the extension.
Make its purpose and setup clear
Provide useful setup, help, or settings in the host app where possible. Describe the extension accurately in the listing and remove prohibited commercial content from it. Keyboard and Safari extensions also need their specific checks under the child rules below.
Test installation, enablement, normal use, and disabling the extension. Give Apple the exact setup route and an example task. A recording can help when the feature is difficult to discover from the main app alone.
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Apple App Review guideline 4.4 Checked 22 September 2026