Transition from UIWebView to WKWebView

UIWebView is deprecated and Apple urges us to switch to WKWebView. Unfortuately WKWebView seems to be still lacking far too many features to be a valid replacement of UIWebView. Therefore I would likt to know if there are ideas how to achieve the following tasks...


Proxy Support

When using UIWebView we could easily route all network through an App-specific proxy. All you need to do is to implement NSURLProtocol for "https" and "https" requests and handle the proxy there. WKWebView does not support NSURLProtocol and does not have any seting for a proxy. Configuring the proxy at system level is not an option, because there's only a proxy setting for WLAN available here, not for mobile internet (G3/G4/LTE), and the systems setting is applied to all other Apps as well.

So all Apps which require their own Proxy can not use WKWebView right now (for example kid-safe browsers which need to filter the web).


Caching, Offline Usage

When using UIWebView and NSURLProtocol it's possible to control all network requests for the main web site and all its resources (images, JS, CSS etc). This is great for implementing a special caching for a real offline mode, so the App remains usable even if there's no internet connection. WKWebView doesn't support this.


Cookie Policy

WKWebView doesn't allow to configure the cookie accept policy.

Replies

Though this was asked a long time ago, it's still relevant and now that the deadline for migration is looming, the answer to this is more important than ever.

Can someone from Apple help by please addressing this and other wkwebview issues ?

With not many tools available to debug wkwebview issues, it becomes quite difficult to get to root causes of issues seen/