Don't know how to use Xcode on M2 Mac Mini

Question

Created Mar ’23

Replies 4

Boosts 0

Views 1.3k

Participants 3

Hi, I've encountered a visual problem in Xcode 14.2 (Release). After adding a C++ File and programming a bit in C++, and more so after adding an .m file, the compile errors are really difficult to read. They disappear after 2 seconds. I think it's worse with .m, but that could be me fantasizing. The issues pane also disappears after one or two seconds.

I googled it and found it to be a known issue that some user claims happens from Xcode 14.0 and up. So I tried Xcode 13.4.1, and I think macos is telling me that my Mac should not be on Ventura for Xcode 13.

So, I'll downgrade the newly purchased Mac Mini, right? That means, I'll do the recovery thing and bring on some earlier OS version than Ventura.

I hesitated, because I just purchased the mini and didn't really want to downgrade the OS. It might make someone unhappy, should I return it.

Another thing I could try, is to read from the compiler output some way, until the other things are fixed? Not sure what to do.

Kind regards

Boost

Answer 1

Markus3 OP

Mar ’23

Have to admit that I haven't disabled live issues in the settings, because I don't know what it would do at all, last time I used Xcode was ages ago. Issues or errors will be shown when a new build is triggered, but I couldn't imagine how well or not this works regarding incremental compilation, because someone wrote that this solution is tedious. The live issue is gone ATM, so, thank you for your consideration and have a happy Xcode.

0

Answer 2

JWWalker OP

Mar ’23

I've never seen the problem you describe, but if the Issue Navigator panel isn't working, you could look in the Report Navigator. But also use Feedback Assistant to file a bug report.

0

Answer 3

endecotp OP

Mar ’23

There's a long thread about this somewhere. I would post a link but I can't immediately find it....

0

Answer 4

Markus3 OP

Mar ’23

It's this thread https://developer.apple.com/forums/thread/715103

I've posted my own description of it here again because I have virtually never downgraded macOS and am totally new to mac things. And because it took 10 minutes unboxing the m2 mac, and another 10 minutes to trigger the bug (after some time to install Xcode, offline).

I'll use the feedback assistant to give my vote for working on the issue, I guess it could actually happen quite often. Will use the Report Navigator, or disable 'show live issues' as they advice in the thread. I didn't know the impact on incremental compilation etc. Pretty sure in 14.3 the issue should be gone.

0