"This bundle is invalid"

We bumped to the latest JUCE (head of develop) from an old one (c768979) and before I spend ages investigating/bisecting has anyone else had this problem reported by apple when uploading an IPA?

I suspect something simple is wrong but it’s not obvious to me. Maybe something is missing from our CMake setup or whatever.

Diffing the IPA contents reveals nothing significant. All signed the same, files in the correct places.

After 20+ builds I have found that this is the commit where it breaks

I don’t know why a VST3 Client related change breaks our iOS IPA but Apple doesn’t like it.

Noticed the same thing recently. It seems the issue is caused by the change in extras/Build/CMake/copyDir.cmake – with just this change reverted, AUv3 validates fine.


Yep that works for me too. Two days to figure this out :frowning:

I wonder how the JUCE team’s own AUv3 plugins don’t have this problem?

In your case @phraemer, is this a GUI app project or an AUv3?

Are you receiving any messages saying why the validation was failed?

@attila an AUv3 project. We use CMake not Projucer.
The message comes in the form of an email after successful upload of the IPA to the app store:

Dear Developer,

We identified one or more issues with a recent delivery for your app, “PLUGIN NAME” VERSION (VERSION.BUILD_NUMBER). Please correct the following issues, then upload again.

ITMS-90018: This bundle is invalid - The file extension must be .zip.

Best regards,

The App Store Team

Not very helpful of Apple as this isn’t even the correct error let alone a descriptive one.

Hey @attila, for me this happens when validating Standalone + AUv3 extension in Xcode. The resulting archive is indeed invalid - the extension is a broken symlink to a temporary build directory.

1 Like

@attila Same here using AUv3, this is definitely a JUCE bug…

1 Like

Fixed here, and included in JUCE 7.0.7.