@JamesC I like this a simple sensible solution I will definitely consider it!

@JamesC ok well note the thread as a question, and then note it as Solved. So when people are looking they see the answer is in here...

Is it the setting actually in xcode then?

Screenshot 2025-09-14 at 06.46.25.png

Then build in xcode rather than in hise?

@DanH cheers for that the AI heavily judged me for not quite having the correct type of certificate and I was able so far to successfully sign the things!

@d-healey thanks for your advice of doing it manually first so everythigns in place solid as always!

@JamesC said in Universal Binary Issues:

thanks for the advice as always will give that temp solution a try once the kids are asleep!

Let me know if it works.

You can't codesign a Mac plugin on Windows, you need to do it on macOS. You'll need a developer account, it's a bit of a fiddly process the first time you do it. There are a few guides on the forum that should come up in the search.

@Chazrox @Christoph-Hart guys thank you, as you've suggested this would be a much better solution.

Hey Guys just to give some updates to this, for sure an xcode issue, I pulled my old mac mini out (Sonoma 14.7.7) and compiled on that and had the same issues come up until I went back to xcode 15.0 and was able to get completed functional vst and au builds out!

Cheers for all the help

@JamesC So it seems in PROJUCER the mac message about paths that has come up a fair bit may have been in the issue, rather than pressing ignore as many of the froum posts suggested I manually pointed things to what it already said and was able to export an AU version this morning!

Thanks for advice yesterday

@JamesC @d-healey as predicted I missed a step, thanks so much for the videos that you have put out there, should have started with them!