_BSMachError XCode 7 Beta

Question

I am getting the following error when I am running my code in Xcode7 with Swift2, after presenting a view controller through a push segue:

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

The other SO articles had no resolution, does anyone know about this issue?

I got the same problem running Xcode Version 7.0 (7A218). Too early to find a pattern; just noticed it. — Frederick C. Lee, Sep 12 '15 at 20:15
Same here... got it now for the first time after setting a breakpoint in viewDidDisappear — DiogoNeves, Sep 22 '15 at 09:29
I also get the same warning using obj c in Xcode 7. How to solve it ? — Hardik Shekhat, Sep 24 '15 at 10:48
I can also consistently reproduce this error by rotating the screen while the on-screen keyboard is up. Xcode 7.0.1, iOS 9.0.2. — j.f., Oct 08 '15 at 21:14
I also have the same issue. No pattern yet. Comes and goes. Not consistent. — Mehmet, Oct 14 '15 at 15:39
I'm getting it in Version 7.2 (not beta) when I rotate my iPhone 6 iOS 9.2. I have two webViews on screen, and am not using the network (at the time of the error). My webViews don't seem to draw as fast, it's not noticeable, but I have some Javascript that measures various things that reports incorrect results at around the same time this error occurs. — narco, Jan 06 '16 at 23:12
I got this message when I present a view inside alertView handler block . — Kiran P Nair, Mar 26 '16 at 09:04
I got same error when appear keyboard, my xcode version is Xcode 7.3.1(7D1014). and my project is based on phonegap, jquery mobile. — sirius2013, Jun 07 '16 at 17:11

score 21 · Accepted Answer · edited Jun 20 '20 at 09:12

Although this problem seems to persist as a bug and will likely be fixed, it stems from the new App Transport Security that has been implemented in iOS 9.

If your application pulls data from a web server, in order to populate the View Controller that you will be presenting, you can resolve these errors by verifying/granting access to the particular site(s) you're pulling from.

In order to address this you will add the following to your App's .plist file:

You may want to alter your ATS Exception Dictionary to fit your needs

<key>NSAppTransportSecurity</key>
<dict>
    <key>NSExceptionDomains</key>
    <dict>
        <key>testdomain.com</key>
        <dict>
            <key>NSIncludesSubdomains</key>
            <false/>
            <key>NSExceptionAllowsInsecureHTTPLoads</key>
            <false/>
            <key>NSExceptionRequiresForwardSecrecy</key>
            <true/>
            <key>NSExceptionMinimumTLSVersion</key>
            <string>TLSv1.2</string>
            <key>NSThirdPartyExceptionAllowsInsecureHTTPLoads</key>
            <false/>
            <key>NSThirdPartyExceptionRequiresForwardSecrecy</key>
            <true/>
            <key>NSThirdPartyExceptionMinimumTLSVersion</key>
            <string>TLSv1.2</string>
            <key>NSRequiresCertificateTransparency</key>
            <false/>
        </dict>
    </dict>
</dict>

More details to this solution can be found here or here The Apple Documentation for App Transport Security is worth reading too.

I've made a simple test app that has no network activity whatsoever, still getting this error. Seems like it has something to do with core layout functionality. Your answer seems irrelevant. — NKorotkov, Nov 11 '15 at 09:12
@NKorotkov the error may spawn from multiple scenarios, see Mark L's answer — mattgabor, Jan 07 '16 at 18:28

score 17 · Answer 2 · answered Sep 30 '15 at 13:38

I had the same two error messages. In my case, the errors were appearing when I called [[UIApplication sharedApplication] openURL:url] after the user selected a button in an open UIAlertController. I assumed the alert was trying to close at the same time I was trying to open the URL. So, I introduced a slight delay and the error message went away.

dispatch_after(0.2, dispatch_get_main_queue(), ^{
    [[UIApplication sharedApplication] openURL:url];
});

Not sure if this helps with your particular problem, but I thought it might be helpful to share.

This handled the problem for me. I was displaying a PDF using the documentInteractionController and adding the delay made the error go away. Thanks! — jroyce, Feb 24 '16 at 14:24

score 3 · Answer 3 · answered Feb 03 '16 at 15:21

3

Change the Localization native development region key in your info.plist from en to United States

answered Feb 03 '16 at 15:21

user1079052

3,803
4
30
55

or United Kingdom :) – jenson-button-event Nov 10 '16 at 18:39

score 3 · Answer 4 · answered Jun 01 '16 at 19:01

Dismissing view controller prematurely might cause this.

[self dismissViewControllerAnimated:YES completion:NULL]; 
//<do something..>

This throws _BSMachErrors

vs

//<do something..>
[self dismissViewControllerAnimated:YES completion:NULL];

Now, the _BSMachError is gone.

score 2 · Answer 5 · answered Dec 15 '15 at 21:51

2

I got these errors when I was using the keyboard. According to this note in Apple Docs, this is somewhat expected.

http://cocoadocs.org/docsets/Keyboard/0.3.0/

answered Dec 15 '15 at 21:51

Mark Lummus

740
8
17

3

I don't think these are the Apple Docs, but docs of a third-party. – NYC Tech Engineer Dec 18 '15 at 16:11
true, this is generated using CocoaDocs, which looks similar to Apple's documentation but is user generated. It is in reference to a specific app designed by Bell App Lab – mattgabor Jan 07 '16 at 18:30

score 2 · Answer 6 · answered Mar 05 '16 at 16:43

2

I make like that

 dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0)) { () -> Void in
        AnswersDataServerEntity.saveSingleDocoment(doc)
    }

answered Mar 05 '16 at 16:43

Alexander Khitev

6,417
13
59
115

score 0 · Answer 7 · answered Jul 08 '16 at 22:00

Having this statement right below IBAction Button was causing the issue.

self.view.endEditing(true)

The issue was fixed in Swift 3, by commenting out the above line and handling the end editing in a different way, or can also be fixed adding the above line after all other code under IBAction.

score 0 · Answer 8 · answered Jul 25 '16 at 11:30

0

I had this problem while debugging and it disappeared when I removed a breakpoint in my response to the view size changing.

answered Jul 25 '16 at 11:30

Paul

1

Welcome to StackOverflow! For future reference, please try to post additional questions like this in the comments section, as this is not actually a solution. Thanks – cdomination Jul 25 '16 at 11:37

_BSMachError XCode 7 Beta

8 Answers8

In order to address this you will add the following to your App's .plist file:

Linked