Re: Issues with WKWebView: "Requestor is not a platform binary"

2015-07-28 Thread Jens Alfke
Also FYI, it’s a lot simpler to serve content to a WebView by implementing an NSURLProtocol, than by embedding an entire web server. (And it doesn’t open any sockets, so you avoid this problem.) I’m sure there’s sample code somewhere showing how to do this, but I don’t have any pointers to it.

Re: Issues with WKWebView: "Requestor is not a platform binary"

2015-07-27 Thread Rick Mann
Huh, interesting. I'll see what I can suss out. I borrowed someone else's code. > On Jul 27, 2015, at 22:36 , Jens Alfke wrote: > > I'll bet the OS is killing your server/listener socket. It does that after an > app's been suspended a while. You'll need to close the socket on suspend and > reo

Re: Issues with WKWebView: "Requestor is not a platform binary"

2015-07-27 Thread Jens Alfke
I'll bet the OS is killing your server/listener socket. It does that after an app's been suspended a while. You'll need to close the socket on suspend and reopen it on activation. --Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please d

Issues with WKWebView: "Requestor is not a platform binary"

2015-07-27 Thread Rick Mann
In order to make an offline viewer for my company's WebGL webapp, I've built an iOS app that embeds a little web server, and serves up the models directly to the WKWebView that requests them. This works well, but in 9b4 it is exhibiting a new behavior. After a time, which seems to do with leavin