LOGIC: version invalid on built plugins in Plugin Manager

[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.

[tomekslesicki]

@DanH of course the best solution would be a proper fix by the one and only @Christoph-Hart

[Christoph Hart]

@tomekslesicki I‘m fishing in the dark as much as you since it has nothing to do with the source code but the build tools provided by Apple...

[Christoph Hart]

So for me it doesn't make a difference whether I'm aborting the HISE export or not, and I'm on macOS 11.2 with Xcode 12.

@tomekslesicki Can you make sure that if you open the Autogenerated Projucer file that it opens it with the same Projucer that is used by the batch export (the one in HISE_ROOT/tools/projucer? It might be possible that you have another Projucer binary floating around (from a more recent JUCE version) that will write the AU version properly.

1. Make sure that the Projucer isn't running and if yes, quit it over the context menu
2. Open the Projucer from tools/projucer (should be 6.13 from 14.12.2021)
3. Remove the Binaries/Builds folder in your project, then open your autogenerated project file and click on Save to export
4. Build it in Xcode (Product -> Build for Profiling)
5. Run auval to check the version (Logic is doing the same so if the version isn't reported correctly there it won't be in Logic).

[Dan Korneff]

@tomekslesicki I have always cancelled the builds in HISE because iLok requires extra Linker Flags to compile.
So we're looking at JUCE or Xcode.

[Dan Korneff]

https://forum.juce.com/t/au-plugin-version-in-logic-pro-x/46992/4

might be relevant

[Christoph Hart]

OK, it seems like it has something to do with the Projucer used - if I download and build the vanilla 6.1.4 Projucer the version is embedded correctly.

I'll build it now, set the GPL flag and update the binary in the HISE repo, then it should work with the HISE export.

@dustbro I could add a Linker flag field in the Project Settings if this is the only thing keeping you from automated builds.

[Dan Korneff]

@Christoph-Hart

Extra Linker Flags:

-Xlinker -headerpad -Xlinker 800

[d.healey]

@Christoph-Hart said in LOGIC: version invalid on built plugins in Plugin Manager:

I could add a Linker flag field in the Project Settings if this is the only thing keeping you from automated builds.

While you're at it you should add

<plist><dict><key>NSAppTransportSecurity</key><dict><key>NSAllowsArbitraryLoads</key><true/></dict></dict></plist>

To the custom plist section for xcode - it prevents issues when doing server stuff from HISE.

I already added it to my fork https://github.com/davidhealey/HISE/blob/development/hi_backend/backend/StandaloneProjectTemplate.cpp#L114

[Christoph Hart]

@dustbro: Actually, it's already there: just paste this into the OSX StaticLibs setting (won't work on Windows though

@d-healey I'll merge it when you make a pull request.

[ulrik]

@Christoph-Hart yes, that solved the issue! :)

[DanH]

@ulrik which one?!

[ulrik]

@DanH LOGIC: version invalid on built plugins in Plugin Manager is no more :)

[DanH]

@ulrik 🥳