App Store 2.5.6 rejection: WebKit and alternative browser engines

By The Draftbit team · Updated
Sources checked

This guide is for iPhone and iPad apps that browse the web or implement a browser engine.

An embedded browser can bring its own review requirements. Under 2.5.6, apps browsing the web generally need the appropriate WebKit technologies. Apple offers alternative-engine entitlements under specific regional conditions, including documented arrangements for the EU and Japan.

Identify the engine you ship

Ask your developer which component renders pages and executes web JavaScript. Check bundled browser libraries and region-dependent builds. We’d distinguish a standard system web view from a custom engine before changing the app.

Match the implementation to your approval

Use Apple’s supported WebKit approach unless the app has the appropriate alternative-engine entitlement and meets its conditions. Applying for an entitlement isn’t the same as having permission to ship it. Consult the linked Apple entitlement documentation for supported regions and obligations.

Test browsing, authentication, and opening external links in the corrected build. Give Apple the engine used and any applicable entitlement evidence. Explain regional behavior explicitly so the reviewer can test the version they receive.

Messages this guide can help with

App Store 2.5.6 rejection; app store 2.5.6 denial; Guideline 2.5.6; WebKit and alternative browser engines

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