Warning Xcode 15

[Christoph Hart]

@ulrik It's working here on Xcode 15 too, but I also remember getting that error once. I don't know what I did to get rid of it, looks like a classic case of subconsciously fighting against the macOS weirdness.

[ulrik]

@Christoph-Hart

[orange]

@ulrik I want to install macOS Sonoma but I'm unsure if there are problems with the current XCode 15 version.

Does macOS Sonoma accept XCode 14?

[Matt_SF]

@orange I had to update to Sonoma for another software : XCode 14 won't work, you'll need XCode 15. But there are indeed reported errors with this version - I'm also having the same issue as @ulrik.

[d.healey]

Xcode Releases

More than you ever wanted to know™

xcodereleases.com (xcodereleases.com)

[ulrik]

@orange As @Matt_SF says, you will need v.15 for Sonoma.
I also had to update one computer to Sonoma and I still have the "Cycle inside MultiSynth....." issue with Xcode 15 :(

@Christoph-Hart do you remember how you solved the issue?

[d.healey]

@ulrik But it says 12.5+ for xcode 14, doesn't that mean anything above 12.5?

[ulrik]

@d-healey

[DanH]

@ulrik Am in the same position!

[orange]

@ulrik That's bad, so Ventura should still stay

[d.healey]

@ulrik I still don't get it, what does 12.5+ mean then?

[ulrik]

@d-healey Where do you see 12.5+ ?

[Matt_SF]

@d-healey Maybe it means : "compatible with anything above 12.5 ... up to the next version, which is 13.0" ?
Just to be sure, I downloaded XCode 14.3.1 and I do get a warning saying that this version is not compatible with my OS.

[d.healey]

@ulrik

[ulrik]

@d-healey Aha, ok I see what you mean, it's a bit misguiding info, I think as Matt says, up to next major release

[ulrik]

@Matt_SF I did what you did, downloaded 14.3.1 and runned the executable inside the package in the terminal, and managed to compile to VST3 and au, I'm not so sure it's wise to do it though

[DanH]

@ulrik I have actually managed to export all formats, au / vst3 / aax ....

[ulrik]

@ulrik Ok I tried some more with Xcode 15, in "Build Phases" tab, the "Shared Code" was at the bottom, I moved it up to be handled first, and bingo, it worked (don't ask me why )
I just searched the internet and found some people talking about the same issue as me.

Moved the Shared Code

to the top in the Build Phases

[Matt_SF]

@ulrik odd, I think we read the same posts! I also tried that but didn't work... I'll try again

[d.healey]

@ulrik Makes sense because the shared code is shared between the other build stages, so if it doesn't exist first those other stages won't work.