AU component version is always 0 in exported plugins (Xcode exporter misses versionAsHex)

[dannytaurus]

Ha. A fix from @DanH is already sitting in a PR in the custom JUCE repo sine June 16th: https://github.com/christophhart/JUCE_customized/pull/3

[DanH]

@dannytaurus nearly all my PRs get ignored

[ustk]

I stopped trying to push PRs because a lot of us are cross fixing the same stuff over and over before having a chance to see them reviewed and merged, unfortunately...

[Christoph Hart]

Sorry guys I‘m currently completely submersed in a theatre project, so this month will still be slow but then I‘ll pick up the work and review / merge all the PRs - just keep them coming they are not ignored but sit around waiting to be reviewed.

[David Healey]

@dannytaurus I just had a user on Tahoe report this issue

Logic Pro's plug-in manager says Libre wave > Rhapsody is compatible but the version is invalid.

Is that related to what you've described here?

[dannytaurus]

@David-Healey Yep. Below shows 'invalid' value from current HISE build, a post-export fixed one and a non-HISE version number.

[David Healey]

@dannytaurus wonder why the issue is only showing up for this one use though.

At least it's a simple fix

[dannytaurus]

@David-Healey

issue is only showing up for this one use

What do you mean? As far as I know all AU plugins exported from HISE since Dec 2021 have had this 'invalid' version in Logic. VST3 is unaffected.

[David Healey]

@dannytaurus It's the first time a user has reported that Rhapsody won't load because of this version issue. Or possibly the user just saw invalid and didn't try and load it on a track - I shall ask.

[dannytaurus]

@David-Healey The AU with an invalid version works fine. It just shows 'invalid' in the plug-in manager.