Search for a command to run...
App includes a web browser or web viewing capability that doesn't use the WebKit framework (WKWebView). Apps that browse the web must use WebKit.
7 cases reported · ~9 days to resolve
Apple's rejection message
Guideline 2.5.6 - Performance - Software Requirements: Your app uses a software rendering engine to display web content, rather than the WebKit framework.
Replace UIWebView or any custom rendering engine with WKWebView. This is the only approved way to display web content in iOS apps.
Guideline 2.5.6 - Performance. Your app uses a third-party JavaScript runtime for executing user scripts that does not use JavaScriptCore.
Fix: Replaced QuickJS with JavaScriptCore framework. For languages other than JavaScript, used sandboxed interpretation with output piped back to WKWebView. Student code runs in JSContext with proper sandb...
Guideline 2.5.6 - Your app browses the web but does not use the WebKit framework for rendering web content.
Fix: Applied for the alternative browser engine entitlement for EU distribution. For non-EU markets, switched the rendering backend to WKWebView while keeping our custom UI and features on top. Users outsi...
Guideline 2.5.6 - Performance. Your apps embedded code editor uses a non-WebKit JavaScript execution engine for code preview.
Fix: Switched preview rendering to WKWebView. Code editing still uses custom syntax highlighting. Preview now runs user code in a sandboxed WKWebView with proper content security policy.