Swift mysterious error

Question

I'm receiving mysterious error messages while debugging my swift app on my iPhone.

This message gets displayed while a performSegue after a Siesta-API-Call:

2016-12-06 11:08:36.032131 dl[20878:6372455] [Common] _BSMachError: port 9913; (os/kern) invalid capability (0x14) "Unable to insert COPY_SEND"
2016-12-06 11:08:36.032664 dl[20878:6372455] [Common] _BSMachError: port 9913; (os/kern) invalid name (0xf) "Unable to deallocate send right"

And this messages pops up after closing the app over the home button:

2016-12-06 11:08:52.609482 dl[20878:6372455] Cannot snapshot view (<UIKeyboardImpl: 0x13fe16770; frame = (0 0; 414 226); layer = <CALayer: 0x17403eda0>>) with afterScreenUpdates:NO, because the view is not in a window. Use afterScreenUpdates:YES.

The started appearing somehow. Any ideas how to fix these?

http://stackoverflow.com/questions/37800790/hide-strange-unwanted-xcode-8-logs — Sachin Vas, Dec 06 '16 at 10:15
Tried that already but without success.. I'm debugging it on my iPhone and the second warning still shows up.. — Kevin H. Klein, Dec 06 '16 at 10:17
Found out that the error was caused by a "Please Wait" AlertController which was not dismissed correctly before doing a segue — Kevin H. Klein, Dec 07 '16 at 19:52

score 4 · Answer 1 · answered Dec 07 '16 at 19:53

4

See last comment..

Error was caused by an "Please Wait" AlertController which was not dismissed correctly before doing a segue..

answered Dec 07 '16 at 19:53

Kevin H. Klein

403
1
5
14

I was not doing a seque but apparently a call to popViewController causes the same error. I fixed it by dispatching all of the code to the main thread asynchronously so it would get run after the alert controller is done/gone/dismissed/destroyed. – David Rector Jan 04 '19 at 19:34

Swift mysterious error

1 Answers1