Post

Replies

Boosts

Views

Activity

Reply to Anyone get a "kill() returned unexpected error 1" when testing iOS 13.2 beta?
If you are having trouble viewing printed information in the command window because of this bug*My work around is to just have breakpoints before and after unique executions that you want to track and using a customized NSLOG for the output with a unique phrase that you can easily search for inside of the command window. If you are running a loop, please use an index to view particular information. Obvisouly there is redundancy in this method, but you can remove break points and you can easily remove a custom NSLog by changing the output to " ... "(no output) when you are finished. Making it easy to activate your nslog later.Example of a unique phrase: "Home Screen ViewController - Array - The Main TableView:";"View Controller - Object Type - To Where"Plenty of ways to do this but its been worth the extra input as we have been hiring other developers and using a lot of code.
Jan ’20