324

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 object in the storyboard.

Then the following message is shown continuously while the web view is visible ...

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

At the moment I close the view I get the following message:

2019-10-10 12:32:41.577505+0200 (...)[ProcessSuspension] 0x1051e50b0 - ProcessAssertion::processAssertionWasInvalidated()

Sometimes I get the following message in the middle while the web view is loaded: (I can't say when it happens)

2019-10-10 12:33:11.453528+0200 (...) Could not signal service com.apple.WebKit.WebContent: 113: Could not find specified service
2019-10-10 12:33:11.459713+0200 (...) Could not signal service com.apple.WebKit.Networking: 113: Could not find specified service

And the if I touch the screen it starts again

    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 
...

I have checked that this is happening in all of the view controllers with WKWebViews of my app, so it doesn't seem to be a code error.

This doesn't crash the app, but I would like to know why this is happening, and if someone else is having the same issue.

L33MUR
  • 4,002
  • 2
  • 12
  • 27
  • I got the same issue but also can't figure out what's happening... I maybe thought it would be related to Timers but that was a negative – krjw Oct 11 '19 at 13:06
  • Same here, I'm also using swiftui and what's weird is if I launch my web view after typing text into one of my swifui TextFields it breaks, but if I don't type anything it works. – Robert Oct 14 '19 at 00:56
  • I see the same issue with Xcode 10.3 and an iPhone with iOS 13.2 beta. – Klemens Zleptnig Oct 23 '19 at 14:53
  • 2
    same issue for me with iOS 13.2 release. Its always a little alarming to me that there aren't more reports of this. Always makes me feel like its something i am doing wrong. This seems like a pretty big issue. https://forums.developer.apple.com/thread/123782 – AndySousa Nov 05 '19 at 15:22
  • 3
    I have same issue on AppKit with WebKit on Catalina 10.15.1 and Xcode 11.2 – Victor Kushnerov Nov 06 '19 at 08:11
  • 1
    same issue hier. I tested different apps. Some applications with ionic 3 crash directly and some show the error but will be opened. But all applications with ionic 4 will crash directly. I created a fresh new ionic 4 app but it is not possible to start the app. – Torben G Nov 06 '19 at 11:18
  • Here our apps crash directly unless we inspect them? So weird. – Eric Nov 13 '19 at 12:43
  • 1
    Does any of you see that the webpage is also not loaded when this error occurs? – Mohsin Khubaib Ahmed Dec 18 '19 at 07:53
  • I am also getting same warning in iOS 13.3 but app behaves as expected i.e. no crash – Surendra Kumar Jan 24 '20 at 13:17
  • 1
    I am still having this issue in iOS 13.3.1. – Jackson Jan 29 '20 at 03:27
  • good job apple, now I can't debug in real ios device. – neobie Feb 01 '20 at 05:26
  • 1
    Have you got any new information on this? - My info: Apple knew about the issue and said they were looking at a possible fix but that was on 18th December 2019 and not been able to get anything more from them about it – akaBase Feb 05 '20 at 14:41
  • So not sure if this helps but obviously I have the same errors and even the newest ios update does not solve it. Today I was designing the interface on mac before pushing it to the ios environment and I noticed the web previewer also gives a lot of error messages being *Failed to load resource: unsupported URL -> coming from gap://ready* I have the feeling this is because of url blocking on local pages, stuff like that. Can this all be caused by some security update on webview which just mangles up the cordova init? – Grit Feb 14 '20 at 08:56
  • It isn't fixed in the latest iOS 13.3.1(17D50) release. Hope it will save someone's time. – Mohit Kumar Feb 11 '20 at 13:01
  • For the other two five eleven macOS developer out there: It’s also **not fixed** in `macOS 10.15.3`. – ixany Dec 15 '19 at 15:02
  • I just read in an apple forum that it should be fixed with 13.4 which should be released this month. Can somebody with a beta of 13.4 double-check that? – Manuel Mar 15 '20 at 16:35
  • Issue still exists in iOS 13.5 – SAHM Jun 25 '20 at 01:08

7 Answers7

214

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

see:

Update:

It's fixed in 13.4 release.

Hvordan har du det
  • 3,605
  • 2
  • 25
  • 48
  • 44
    iOS 13.2 _release_ did not fix it. And it’s throwing exceptions. it looks like it’s logging every 10ms (100 per second) this will chew up log files quickly.. smh – Roy Lovejoy Nov 01 '19 at 14:57
  • 5
    I have same issue on AppKit with WebKit on Catalina 10.15.1 and Xcode 11.2 – Victor Kushnerov Nov 06 '19 at 08:11
  • 8
    13.2.2 still showing continuous output for me, thousands of times over. I suspect it may have something to do with a WKWebView touch or scroll event but i am still troubleshooting. Horrible though, to say the least. – DevMike Nov 07 '19 at 18:54
  • Under IOS 13.2.2 it is not logging continuously but with each process only briefly. It logs 50 to 60 times and then stops. When the next process is started, 50-60 logs again. – desmeit Nov 08 '19 at 08:52
  • It seems to me that this also happens each time when a JavaScript bridge (WKScriptMessageHandler or something) is used or when evaluateJavaScript is called from ObjC. Our most important app (highly visible on the App Store) is seriously affected by this issue as well. – Seven Systems Nov 08 '19 at 11:34
  • I tested this project as well. its a simple xcode project with a wkwebview (without cordova or something). It's got the same issue. We're gonna have to wait for apple. https://github.com/wayou/WebViewExample – desmeit Nov 08 '19 at 12:52
  • @desmeit for me in 13.2.2, i am actually seeing continuous and endless output in my webview which includes a looping SVG animation. When i remove the SVG, i only see the errors fire after/during a touch or scroll event. – DevMike Nov 09 '19 at 11:30
  • Same error, apple update has no published CVE entries. It is not clear what it is connected with. – Anonimys Nov 12 '19 at 13:03
  • 12
    13.3 beta did not fix it as well – Eric Nov 12 '19 at 20:08
  • 1
    For workarounds see [Comment in Ionic Issue 17494](https://github.com/ionic-team/ionic/issues/17494#issuecomment-492647992) – Peter Scott Nov 14 '19 at 12:03
  • @PeterScott how is this related? – plocks Nov 14 '19 at 13:37
  • For me I was seeing exactly these symptoms and the removal of the background css resolved it. From the comment previous link I came . across Safari bug that looks to me to be root-cause. Removing the background image css eliminated the blinking, ios crashes and the debug streaming observed in slightly different circumstances. – Peter Scott Nov 14 '19 at 16:04
  • 2
    How about 13.3 beta 2? Still not fixing it? – TuaimiAA Nov 15 '19 at 22:58
  • 17
    The problem is first reported on Sep. 24, 2019. But I am wondering why this issue is not getting much attention and a rapid (released) fix! Many has reported that this problem is present in both XCode and downloaded apps. Also, some reported that this problem is crashing their apps no matter what. Honestly, I started now questioning the reliability of developing native apps on top of cordova/capacitor/ionic. – TuaimiAA Nov 15 '19 at 23:33
  • I am too facing this issue and WKWebView does not display the AnnotationView. It is working through xCode 10. – Manish Nov 27 '19 at 10:19
  • 1
    not really an answer, but adding some observations. for me this works on the simulator, but I get this exact error if I try to run on an actual iPhone. (iOS 13.2.3) I also notice that webView?.loadFileURL(allowingReadAccessTo) has a weird bug... If I call this with a particular folder hierarchy in allowingReadAccessTo, it works for this call. If the next call has a different folder url for allowingReadAccessTo it will NOT work... it only has access to the first one. I just wonder if the two are related somehow? – Paul Stevenson Dec 04 '19 at 01:39
  • @PeterScott did you manipulate it using Swift code? My page is not loading as well as I cannot proceed further.. – Mohsin Khubaib Ahmed Dec 18 '19 at 08:05
  • 5
    Same problem in iOS 13.3 final release – David Toledo Dec 21 '19 at 19:33
  • I'm having these errors but my app isn't crashing, at least on the only device I have to test with. I'm trying to create UI Tests using the XCode recorder to upload to AppCenter Test Cloud but every time I touch the screen during recording XCode crashes, I think it's related to this issue. – Post Impatica Jan 07 '20 at 20:27
  • Found it on iOS 13.3, real device. – Zhou Haibo Jan 31 '20 at 06:35
  • 8
    Not fixed even in iOS 13.3.1, same warning log appearing. – Abhishek Aryan Feb 10 '20 at 17:52
  • Getting it on 13.3.1 on real device ( iPhone X) – Clint Mar 06 '20 at 19:47
  • 5
    Fixed in iOS 13.4! – balslev Mar 26 '20 at 09:38
  • 1
    I can confirm that in macOS Catalina 10.15.3 and XCode 11.4 this error exists. I am working my way through a macOS app course book and as soon as I added WebKit this error appears in the console in subsequent builds. – SouthernYankee65 Apr 14 '20 at 21:59
  • I just ran in to this testing on a real iPhone on 13.3.1 with Xcode 11.5 - my question though is what about users who have not updated? Is this error ONLY with Xcode and the iOS 13.2/13.3 versions? Or will the compiled app submitted to an app store crash for users who are still on 13.2/13.3 ? I changed the Schema to not auto-run on app install, and then later clicked app to run to attach to Xcode but it never did. – rolinger Oct 21 '20 at 02:41
64

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

enter image description here

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!

TuaimiAA
  • 973
  • 6
  • 15
7

iOS 13.4 has removed this error! Hurray!

balslev
  • 331
  • 4
  • 11
  • 1
    I can confirm, the message has gone after installing 13.4 – mwarren Mar 26 '20 at 22:29
  • 1
    I am seeing the issue in iOS 13.5 – SAHM Jun 25 '20 at 01:09
  • 13.5.1 face same issue – famfamfam Aug 07 '20 at 08:07
  • I think the fix is Xcode 11.5 and iOS 13.4 - thats what I was interpreting from all the reading. However, if an app is deployed to app store with Xcode 11.5, and users iphones are still on iOS 13.2/13.3 - will the app crash for them? Or is this just a Xcode debugging thing? – rolinger Oct 21 '20 at 02:46
3

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.

Steve Heffern
  • 97
  • 3
3

Update as of 28 March 2020

Finally Apple deployed something, which not only doesn't shows the error in the logs, but actually allows us; developers to compile, run and submit an application.

Especially, if it's you're coming with Cordova/PhoneGap app combined with any HTML5/JavaScript framework/game (Ionic/Phaser) which wants to run on iOS as web wrapper (my personal experience related to this issue) by using WebView. However, not sure if the same issue applied to NativeScript/React Native or native Java/Kotlin/Swift - these don't need a web wrapper to run.

Nevermind, please update your iPhone/iPad to iOS 13.4 and (!!) Xcode to 11.4. Both of them have been released 3 days ago and can confirm that my Cordova-wrapped app doesn't has the log anymore and doesn't crash.

For historical reasons I'll write a note - the affected iOS versions were: 13.2.X, 13.3.X including its betas. If you're reading this after some time - you need to get rid off those by upgrading to a higher version than 13.3 (recommended) or downgrading to lower version than 13.2 (not recommended). The second option you can use only if Apple for some reason would block you with further updates, e.g. your iPad/iPhone will be really old.

Daniel Danielecki
  • 8,508
  • 6
  • 68
  • 94
2

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.

George
  • 25,988
  • 10
  • 79
  • 133
  • interesting solution.. but I need to use the DynamiclLinks... so can't really remove it – mikey Jan 14 '20 at 01:52
  • @mikey Yeah, I know. At least this shows the cause of the issue. For now you can safely ignore it as long as your Dynamic Links work properly. – George Jan 14 '20 at 08:25
  • I only started seeing this after adding in AdmobFree, which probably uses firebase in some way – SimonBarker Mar 19 '20 at 18:04
1

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

Sami Boudoukha
  • 539
  • 10
  • 25