LOGIC: version invalid on built plugins in Plugin Manager

[d.healey]

@tomekslesicki Looks very similar to this error I was getting (on my Intel Mac Mini). My solution was to roll back to an earlier version of Xcode.

LLVM Error building on OSX

I'm getting an error I've never come across before on MacOS. It occurs during the linking and I see that all my system memory is being eaten up by the linkin...

Forum (forum.hise.audio)

[Casey Kolb]

Running into this issue as well. Starting to get complaints from Logic users because it has to rescan the plugin every time due to the version being “invalid”

[DanH]

@Casey-Kolb All I could find online so far: https://forum.juce.com/t/au-plugin-version-in-logic-pro-x/46992/4

Would be great to get this fixed :)

[DanH]

@DanH the commit from 30th November 2021 works fine fyi - I just happened to have that still on my machine

[tomekslesicki]

Ok, I have a little breakthrough:

The last XCode that can build plugins or HISE at the moment is 13.2.1

When the AU is built from HISE, the AU version is not written properly and auval can't process it.

When the AU is built from the autogenerated projucer file, everything is fine.

@Christoph-Hart ?

[Christoph Hart]

@tomekslesicki Great news, we're getting close (I can't find anything in the source code so I think it might have something to do with the build tools).

What happens if you run the batch file (Builds/batchCompileOSX) manually? Does the AU version work then or do you need to go into Xcode for compilation? It might be the case that the command line build tools (xcodebuild) is using a different Xcode version, otherwise there shouldn't be too much difference.

You can check this with a terminal command:

Which version of Xcode does xcodebuild use?

I have installed both Xcode 3.2 and Xcode 4.0.2 on the same machine, which uses Hudson for automated CI (continuous integration) builds. When I say that both were installed, what I mean by that is ...

Stack Overflow (stackoverflow.com)

Is it the same version than you're using manually?

[Christoph Hart]

Or are you using a different Projucer binary than the one shipped with HISE?

[tomekslesicki]

@Christoph-Hart I'm using a different Projucer to compile, the one that came with HISE can't be run and I remember there's a way to hack that but I just downloaded a copy from JUCE back in December I guess. Here's what I'm using:

I only have XCode 13.2.1 installed, I remove all other copies not to get confused ;-)

[d.healey]

@tomekslesicki

I remember there's a way to hack that

It's just a permission issue. You have to run this command: terminal command "xattr -cr" + path to projucer

But I have the same AU version problem with the same version of Xcode and Projucer from the HISE repo.

[ulrik]

@d-healey I have the same problem as well.

[Christoph Hart]

OK, just to summarize:

• Xcode versions do not matter
• if you open the Autogenerated file in the Projucer shipped with HISE, it doesn't work.
• if you open the Autogenerated file with a Projucer built from JUCE directly, it works.

Does it also work with the Projucer 6.1.3 from the JUCE repo? Using a 6.1.4 Projucer with a 6.1.3 JUCE codebase might lead to other issues.

[tomekslesicki]

@Christoph-Hart

• I wouldn't say XCode doesn't matter - nothing will build on versions newer than 13.2.1 ;-)
• it works with the Projucer that comes with HISE, I just tested so I'm not going to test the other Projucer build to save some time
• it doesn't work when building from HISE - I need to manually open the autogenerated projucer project and build from that to get the version embedded

[DanH]

@tomekslesicki @Christoph-Hart using the projucer that come with HISE (6.1.3) doesn't work for me. I can't find the one from the JUCE repo - can anyone link me?

[ustk]

@DanH https://github.com/juce-framework/JUCE/tree/master/extras/Projucer/Builds

[DanH]

@ustk at the risk of sounding rather silly, I can't see a way to download the project in order to build it natively

[DanH]

@DanH gentle enquiry into if this fix is progressing... :)

[Casey Kolb]

@DanH Yep, getting loads of support tickets about this now. Starting to become a more pressing issue. Logic's rescan of CUBE on every open is starting to make the plugin look bad

[Dan Korneff]

I've gotten a few support tickets as well. Gonna try to take a look this weekend.

[tomekslesicki]

@Casey-Kolb @dustbro I had the same thing, the fastest temporary solution was to cancel the AU build in HISE, open the autogenetated Projucer file and build from there. It seems to write the version number properly this way and Logic doesn’t rescan it every time anymore.

[DanH]

@tomekslesicki that might depend on your version of Xcode / OS X. I’m on Mojave and Xcode 10.4 and this solution doesn’t work for me.