XPC connection interrupted in Xcode 7 for iOS 9

Question

I recently updated to Xcode 7 and upgraded my iPhone to iOS 9. I have developed and released an iOS app that had worked perfectly fine on the latest version of iOS 8 and Xcode 6.

Upon trying to go through the process of updated the app for iOS 9 support, I am getting the most ridiculously strange error that has left me baffled.

I have done all the syntax corrections automatically through Xcode, and now my app builds properly. It even runs fine at first.

I have a button that segues to a view controller with a WebView. This view controller loads a link that will display either an image, website, or video from youtube. The content is loaded perfectly fine as always. However, the program will crash and reboot the simulator (and my iPhone) and send me to the lock screen when I click the Back button (I am on a navigation stack).

In Xcode, I get the following messages:

XPC Connection Interrupted. Terminating since there is no system app.

I have Flurry analytics integrated in my app by the way, not sure if thats an issue.

How can I fix this issue? My searches for XPC connections do not seem to return problems similar to mine. I do not even have a clue what an XPC connection is, so why is this in my app anyway?

EDIT: I have found a workaround for the issue. I cannot really say it is a fix.

The crashing was occurring during the use of the method self.navigationController?.popViewControllerAnimated, when set to true. I happened to set this to false, and the crashing stops (now the transition looks awful).

I do not know why this works, and just adds to my confusion.

Alesha

What version of OSX are you running? – Incandesce

I'm running the latest version of Yosemite – Alesha

I am seeing a similar issue when doing [self addChildViewController: child] I have been unable to find a fix or work around as of yet. I'm on Capitan, xCode 7, running on an iOS 9 simulator. If I drop the simulator to 8.4, this problem does not occur. Still hunting for solutions. – Calfee

I am having the issue when I try to do a storyboard segue to a UINavigationController. It doesn't matter whether I use show, or present modally, animated or not animated. If I try to segue programmatically, still get the crash. I created a button in code, and tried a segue, still restarts the phone. I even made a different view controller, and it crashes every time I attempt a segue. – Pompeii

See also this answer on a different question -- same error message, entirely different solution: https://mcmap.net/q/302739/-swift-xpc-connection-interrupted-and-app-freezes – Regan

For my case, I totally uninstalled the app, then install it again rather than just override installing, the problem was gone – Lunarian

Answer 1

The problem lied in the storyboard for me as well. I created a new project and laid out the views and everything seemed to be working fine. I found these couple lines in the storyboard source (right click on storyboard and select view as -> source code) which weren't common between the working version and the broken version:

<keyCommands>
    <keyCommand/>
</keyCommands>

I have no idea what those lines are supposed to do, or how they crept into my storyboard file, but they were what was crashing the app so hard that the phone had to restart. I removed those lines from my main project and everything worked again.

Cusk

Could you please help me in finding where that code can be located? I would like to delete it as well and see if that fixes the issue, perhaps then being able to confirm this the answer to my question. – Alesha

Right clicking the storyboard file and view as source code. Don't search for <navigationItem> just look for <keyCommands> and comment it out or delete it. Just worked for me too thanks a lot. – Gusman

Answer 2

This error can be caused by executing a loop repeatedly. In my case it was a 'for' loop in which I reset the counting variable. As soon as I added an NSLog in the loop it was obvious.

Russel

Answer 3

I just faced the same problem. I don't know if that will help you, but I also think it's coming from the Storyboard:

In my case, the problem is coming from a UITextView. Whenever I try to change the default text inside it, I have this error. If I let the default text or leave it empty, the app works fine. Making an IBOutlet and changing the text programmatically works as well.

I tried with other UI elements, but only the UITextView seems to have this issue.

Muslin

Answer 4

I have struggled with exact same error. Through a process of elimination I established that it had nothing to do with the any class but had to do with the storyboard. Luckily I keep regular backup copies and I tried to compare storyboards to establish what I had done - but could find nothing obvious. The backup copy worked fine and I was able to copy my controller classes (from the faulty copy with the changes) into the backup copy and they worked fine.

I think there is a bug possibly in storyboards.

Curculio

Answer 5

I have same error message when I place a subview in -layoutSubviews method:

-(void)layoutSubviews
{
    [super layoutSubviews];   
    [self populateByImageViews];
}

It causes infinite cycle of layout process and crashes app. Don't place subviews in this place!

Loyalty

Answer 6

Deleting UITextView from the one of the view in Storybord removes the error in my case.

Tibbs

Answer 7

When using QLPreviewController, I am confronted with this problem. Error messages as follows,

XPC connection interrupted
_BSMachError: (os/kern) invalid capability (20)
_BSMachError: (os/kern) invalid name (15)

Since XPC means OS X interprocess communication, so I think this can solve the problem, especial when updating the UI

dispatch_async(dispatch_get_main_queue(), ^{
    // do what you want to do.
});

For Swift 4+, user

 DispatchQueue.main.async {
      //Your Code
  }

Federalist

Answer 8

In valueChanged: method of a UIControl, I had the same problem so I made the code inside valueChanged: to run in main thread and it solved the problem.

@IBAction func valueChanged(sender: AnyObject) {
  dispatch_async(dispatch_get_main_queue(), {
  //code
  }
}

Dorty

Answer 9

For me was some missing constraints with a UISearchBar, but the error was only in the simulator.

I only add some constraints and works better

Dermott

Answer 10

For me it was xcode live issues caused by IB_DESIGNABLE

If you have any IB_DESIGNABLE in source files, the system's live tracker will check for issues in StoryBoard too. It may leads to unnecessary building.

To disable it-

Open Storyboard file. Editor -> Automatically Refresh Views (Uncheck)

If you needs to Disable Live issue tracking

XCode -> Preferences -> General -> Issues -> Uncheck Live Issues

Reference

Tonguelash

Answer 11

My issue probably originated with some storyboard issue, but I cleaned the project, restarted Xcode AND restarted the simulator app and that fixed it.

Pix