Going slightly mad…? `print()` statements no longer showing in the console. But OSLog and NSLog do still work. Super weird! Laptop restarted, derived data cleared..
huh, found it. If you "wait for the executable to be launched” then `print` doesn't reach the console any more.. TIL

@iandundas
I got caught by this recently, but I didn't realize that NSLog/OSLog would still appear, so I just went full fuck-it and started logging to a random label onscreen.

Good to know there's a less stupid thing I could've done