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

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

[David Healey]

Yeah the fix works

[dannytaurus]

@David-Healey Nice. Did you do the JUCE fix? Or the post-export manual fix?

[David Healey]

@dannytaurus I pulled in Dan's PR and rebuilt Projucer

[ustk]

In PluginDoctor it's saying v0.0.0 (before the fix) so it kinda stands for "invalid". I'll report to DDMF so it shows a "invalid" string of some sort as well...

[dannytaurus]

@ustk Yeah, good idea. I asked Claude if the version reports as an invalid number, or just as 0.0.0.

• The AU plist has AudioComponents.version = 0.
• Pluginval decoded that as v0.0.0.
• JUCE’s decoder explicitly formats the packed integer 0 as 0.0.0.

0.0.0 is valid as a semantic version, but AU metadata uses a packed UInt32, not a SemVer string.

In practice, hosts treat raw value 0 as “version unset.” Logic therefore labels it invalid, while pluginval merely displays the decoded value.

For 0.0.30, the AU field should contain integer 30. The bundle’s separate CFBundleVersion can remain the string 0.0.30.