Why I get the console warning: [Process] kill() returned unexpected error 1 when I load a WKWebView in iOS13.2?

Question

Since I installed the iOS 13.2 beta, I have been getting a debug console error message. It happens every time I load a ViewController with a WKWebView objec

Answer 1

I will pre-admit this is a terrible "answer" but it is a valid observation. This has something to do with sandboxing. If you rebuild your app without a sandbox, there are no messages. If you turn on the sandbox and enable Outgoing Connections which is all I need for my app, every mouse event in the webkit gives me the unhappy message.

If I also include Incoming Connections, just as a test, same messages.

Remove the sandbox (for an internal use only app), no stupid messages. Perhaps this observation will help someone at Apple track this problem down some more.

Answer 2

It's a bug in WebKit (or the underlying OS itself). And no, it was not fixed in 13.[2,3] release.

see:

• https://bugs.webkit.org/show_bug.cgi?id=202173
• https://www.mail-archive.com/webkit-changes@lists.webkit.org/msg146193.html

---

Update:

It's fixed in 13.4 release.

Answer 3

iOS 13.4 has removed this error! Hurray!

Answer 4

I don't really know why this affects it, but hey ¯\_(ツ)_/¯

I am using Firebase - and here was a line in my Podfile:

pod 'Firebase/DynamicLinks'

After removing that, I no longer got these logs. Strange, but it works I guess if you don't yet need this pod for now.

This may also be an issue for other pods, who knows.

I have that line in my Podfile for a feature I am yet to implement, but can't until I get a full Apple Developer Membership account.

Answer 5

As in the accepted answer, this is a WebKit bug and it seems that it has been fixed but not released up until the latest iOS release 13.2.2 (at the time of writing this answer) has been fixed in iOS 13.4.

As a workaround, however, you can disable/hide the logs temporarily as mentioned in an answer by @iDevzilla:

1- From Xcode menu open: Product > Scheme > Edit Scheme

2- On your Environment Variables set OS_ACTIVITY_MODE = disable

This will ONLY hide the logs so you can continue developing and testing on iOS. As some indicated, this problem crashes their apps no matter what (for me it is not until now). Also, be careful using this method as it might hide important error messages!

Answer 6

Note that you have to use both iOS 13.4 on your device, and Xcode 11.4, otherwise, you'll still see the logs.