Howdy. Been searching the forum for a solution to this, but not getting much joy beyond Use CMake instead…. I’ve been looking at 10 year old threads on this topic, so was hoping someone might be kind enough to update me on the latest position with this issue.
iOS works absolutely fine (aside from having to manually copy the dSYMs), but the macOS archive is weird, for want of a better term, including a Users sub-folder in Products 
I guess that’s related to the Binary Location stuff in the Exporter config somehow.
Other than use CMake instead, anyone managed to get Xcode to create valid macOS archives from Projucer projects, or is it borked for the foreseeable?
Thanks, -Rob @ WI
Be great to know if I’m missing something, or if this is a known issue, and there’s a workaround please?
In summary, when I create an “empty” basic plugin project for Projucer, fill-in the appropriate bundle and developer IDs etc., and load up the Xcode project for iOS - all is fine - I can create valid archives. However, the macOS project creates “odd” archives that Xcode does not recognize as being valid, so shows them as “generic archives” in the Organizer window. When you look in the actual archive, the contents are “odd” as per earlier comment. This means currently (perhaps just for me?) I can’t validate the macOS archive with the App Store, as I can with iOS.
Quite possible I’m doing something stupid (won’t be the first time) but it’s a head-scratcher given that iOS pretty much works right out of the box. Which is great!
Any info please? Anyone? Thanks, -Rob @ WI
I haven’t tried doing an archive in macOS for a very long time. You mention a basic plugin project, are you looking to share an AUv3 on the AppStore? I think few people currently do this as you can’t distribute the other plugin formats that way so I think people just aren’t using the AppStore as much with macOS builds.
Hi @anthony-nicholls - yes, although to be specific, AU(v2) on macOS, and AUv3 on iOS. iOS is working fine, but I’d like to make those plugins also available on macOS as a “universal purchase” on the App Store.
To the best of my knowledge you can’t distribute AUv2 plugins on the App Store. You can only distribute apps, and you can/must deliver an AUv3 as part of an app. It’s also worth noting that no application distributed on the App Store can load an AUv2 plugin (except those made by Apple) as it’s not possible to load AUv2 plugins in a sand boxed application.
I think because of this there aren’t a lot of developers delivering plugins via the AppStore on macOS and hence why there probably aren’t a lot of developers that need to archive their macOS builds.
OK, I was hoping it would work like iOS does (silly me…), in so much as you do actually distribute an app, which contains its AudioUnit extension(s).
TLDR: pointless exercise? 
Thanks for the info though - much appreciated.
1 Like
