Bundle is invalid when submitting to App Store Connect

I am attempting to submit my first MacOS application to the App Store Connect. I have gone through all the steps in the documentation and used Packages to create my PKG flat file. Here are the issues:
Validation failed (409). This bundle is invalid. Scripts archive is present but unused (no script references in PackageInfo).
I have found no reference to a scripts archive anywhere in the info.plist or other files within the package. I’d sure appreciate any recommendations where to look to resolve this error!

Thanks in advance.

I wound up using App Wrapper 4 to submit my MacOS application to the Apple Store. It seems to be nearly impossible to do so with any other tools - well worth the cost of that utility.

In packages, did you specify a pre or post install script?

What version of Xojo are you using? Xojo 2025r1 has a new Publish feature that handles all the process of submitting the macOS app to the App Store Connect (including the creation of the pkg file)

Hi Greg,

I don’t do any pre or post install scripts.

Thanks.

Hi Javier,

I haven’t upgraded yet but will do so now that I know!

Thanks for the help.

I had my first review from Apple of the MacOS application - they are insisting on integrating their in-app purchase process. Does XOJO provide any integration of their StoreKit 2 routines? Looks like OWStoreKitBridge offers some of the functionality but am wondering if there is any native integration. Going to install the new version today to explore the Publish feature and any other enhancements that might help get Apple’s approval.

There is not

It’s not native, but MBS StoreKit may be an option for you.

Heads up that I just ran into this issue when submitting to the iOS App Store.

#78860 - [2025r1 Regression] iOS Publishing Fails Due to Invalid Bundle

See this newly created ticket for details as well as how to work around this issue. Although not the exact same issue as Bruce’s, mentioning here as I this thread came up when I started looking for answers to my own specific issue.

I’m surprised that manipulation didn’t break the signature honestly.

The fix will be available in the next 2025r1.1 beta build. Please, don’t hesitate to test it and send feedback to us!

Ah you might have missed that the workaround was applied to the IPA file (not signed and sort of transport file format like a DMG) and not the actually signed .app binary itself.

Awesome news and many thanks Javier for a quick fix. I’ll definitely test things out under the next 2025r1.1 beta build.

Oh. I thought you were manipulating the bundle. Then someone should be able to create a post-build script to fix that in older IDEs.

1 Like