Anyone get a "kill() returned unexpected error 1" when testing iOS 13.2 beta?

Started seeing this whenever web views are shown. Also curious about the cause of it.

You're right. It has to do with WKWebViews. Perhaps after rendering a webpage, iOS tries to kill some process and it fails? It does try many times (over a 1000 times in less than 20 seconds, until the webview is replaced with another component)

The same executable if run on iOS < 13.2 does not cause the error message at all.

Thanks,

Neal

I am seeing this almost continuously in XCode with iOS 13.2 today - I am using a WKWebView in a cordova app.

Have you found out any more about this issue? I am getting swarms of these errors logged in XCode whenever i do anything with the app.

The exact message I see is:

[Process] kill() returned unexpected error 1

Any help or ideas would be great.

Hi Jeffree,

This is clearly an issue with iOS 13.2 beta and not Xcode. Opening up the console and running my freshly downloaded app from the app store on an iOS 13.2 device, reveals the same issue: Many "kill() returned unexpected error 1" are generated every second if a WKWebView is being displayed.. What process it's trying to unsuccesfully kill is still a mistery. Once I move to another view, the unsuccesfull kill messages stop.

Thanks,

Neal

I'm also seeing this continuously pop up in XCode beta (11B41)

It seems to only happen when the webview paints. If I leave the app alone, and the page has no animations running, the errors stop flooding the console...

I'm getting the same error when I downloaded iOS 13.2, Cordova project

I'm having the same issue at the moment I load a view controller with a wkwebview inside. Suddenly I get the error several times in a just second.

Also I have started to see this today since I installed iOS13.2 Beta and Xcode Version 11.2 beta (11B41)

...

    2019-10-10 12:10:47.867830+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:47.908698+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:47.908814+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:47.934169+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:47.947668+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:47.964375+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:48.193556+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:48.193723+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:48.193941+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:48.194012+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:48.195679+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:48.200432+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:48.207225+0200 (...) [Process] kill() returned unexpected error 1
    2019-10-10 12:10:48.207298+0200 (...) [Process] kill() returned unexpected error 1

...

Also seeing thousands of these errors if a scenekit view is visible. 13.2 beta.

I am now seeing these in the latest Catalina beta. I get one for every mousemove event in a web view.

Even worse with new 13.2 beta! Is there any way to stop this. The console is now unusable.

I noticed this messages since iPadOS 13.2 beta 3, though they may have been there before. They are not limited to WKWebView, I also get them (thow fewer) with some other types communications with services, such as using UIActivityViewController or simply switching apps. With WKWebView they are much more frequent than just one per second, but they end eventually (only to restart with the next request). I don't see them when using SceneKit, as ally reported here. Other than cluttering up the console, there does not seem to be any harm. Released iOS 13.1.3 does not seem to be affected.

Did somebody figure out where they come from and how to avoid them?

Still persist on iOS 13.2 official, Xcode 11.1.

I counted lines while using a WKWebView in the app: 6162 occurrences in 3 mins, ≈30/sec.

I'm dealing with the same issue.

13.2 is now live without an Xcode update also.

Cmon Apple.

+1 same here ... WebView and also while scrolling page content inside of it it generates even more of these errors

XCode 11.2 beta + iOS 13.2

This seems to have been addressed with a bug in WebKit, but it does not seem to be reflected in the official release version of iOS 13.2.

This message is also displayed in the official release version of iOS 13.2.

https://stackoverflow.com/questions/58321114/why-i-get-the-console-warning-process-kill-returned-unexpected-error-1-when

Still receiving the error with the release of XCode 11.2 and release of iOS 13.2

Same here, running a web view inside a Unity-based app.

I have same issue on AppKit with WebKit on Catalina 10.15.1 and Xcode 11.2

same here basically makes the console log useless

Here as well, I see this filling up my Xcode console while running on device (iPhone X / iOS 13.2 / Xcode 11.2.1) for any WKWebView. It does not happen in the simulator, so it must be specific to iOS on device.

When I check the device logs in the console app, I see the following line always preceding the 'kill' line:

This particular WKWebView was rendering a PDF. For other WKWebView's I always see the 'usesStandardContentView is NO, bailing' preceding the 'kill()' log entry.

Not sure if that is a coincidence, or the cause of the issue. In any case, these errors got added to WKWebView.mm over the last year.

I am experiencing these errors as well: iOs 13.2, xcode 11.2, cordova-plugin-wkwebview-engine v.1.2.1. Interestingly, I do not see these errors when running on the simulator, just the physical device.

I'm having a similar issue. I built an iPad app which is now 3 years of work. My iMac had to be rebuilt so now I'm on Cat Beta using Xcode 11. My app works in the simulator iPad 9.7 but, when I try to port it into a real iPad for testing it gives me the ERROR 1. Could not attach to pid: 1695 - and others. And does not work. Apple Support sent me here. Do you have any idea if this is signning issue? I'm still a novice trying to finish this app. Thanks Mark Herrick - Major Harmony LLC

I'm seeing this a lot and I'm not running XCode at the moment, so it's not related.

Comments on this

https://stackoverflow.com/questions/58321114/why-i-get-the-console-warning-process-kill-returned-unexpected-error-1-when

suggest that removing background image css will stop the errors.