Error '_BSMachError: port 1607; (os/kern) invalid capability (0x14) “Unable to insert COPY_SEND” in Cordova app on iOS 10

Question

Everything works fine till I build my cordova application with Xcode 7.3.0 but it started crashing only on iOS 10 devices after building the same application with Xcode 8 wh

Answer 1

I was getting this error, tried every solution in this thread, and nothing worked. I had a seemingly unrelated UIColor (color out of range) error that I fixed and this COPY_SEND issue went away, too.

The specific UIColor error was UIColorBreakForOutOfRangeColorComponents.

Answer 2

I ran into the same problem during iOS10.0 beta phases, and it seems to still be present in Xcode v11.

There are actually 2 separate errors :

---

1. First of all, as Avaan commented, you have to set all the privacy usage in the info.plist. I believe it is the cause of your crash.

Since iOS10.0, it is mandatory to explicitly tell the user what features of the phone you will use, and for what reasons.

---

2. Regarding the error :

BSMachError: port 1607; (os/kern) invalid capability (0x14) "Unable to insert COPY_SEND"

I resolved the error with this little workaround :

1. Go in Project Settings/General -> Deployment info, check all orientations.

2. Build and run, the interface should rotate according to the device orientation.
3. Undo what you just did (uncheck orientations you don't need). Build and run again, the errors should not appear anymore.

I hope this helped

Answer 3

I received precisely this error carrying out reset of Core Data but none of the above solutions worked or was relevant in my case. Turned out to be result of code taking place inside action of UIAlert which needed to be pushed into main thread. Solution found through here - Error _BSMachError: (os/kern) invalid capability (20) after receiving remote notification on CloudKit record addition - and updated below for Swift 4:

alert.addAction(UIAlertAction(title: "Reset Now", style: UIAlertAction.Style.default, handler: { action in
            DispatchQueue.main.async {
                // Core Data reset code goes here...
            }
}))

Answer 4

I suddenly had this error using the iPhone 11 pro simulator while it was working fine everywhere else (other simulators and actual devices).

The solution for me was to reset the simulator by choosing Hardware > Erase All Content and Settings...

Hope it can help some others in the same case.

Answer 5

I got this when adding a Info.plist key without a matching string. In my instance I added NSLocationAlwaysAndWhenInUseUsageDescription without a description. Accessing the permission dialog cause this error to occur. Adding a string value resolved the issue. iOs11.

Answer 6

For me the cause was [myTextField becomeFirstResponder]; placed after the initial viewWillAppear thread ended.