On Sep 2, 2015, at 12:21 , David Durkee <da...@dwdurkee.com> wrote: > > I’m trying to build three targets for my Mac application that are nearly > identical, and that I want to have the same app name.
I’m happy to be corrected if wrong, but I don’t think it really matters what you do in Xcode, since the actual app bundle name (as seen by users) is always determined later on. Therefore, you may as well give your targets 3 different names, and let Xcode do its default thing of giving the executable files 3 different names, and nominally giving the built bundles 3 different names. This is what you will see during testing (that is, when running a target from Xcode), but *you* don’t care about the names at that point. In order to release an app to others, you’ll need to archive the app in Xcode, then extract the app bundle from the archive (for the non-app-store version) or submit the app bundle from the archive (for the app-store-version). In the first case you go through a Save dialog to give the app bundle its final name (or you can give it any name and rename it yet later in the Finder before you give it to any users). In the second case, I don’t think it matters what the bundle is called, because the App Store is going to deliver it to users under the name that’s in the iTunes Connect metadata, which is independent of the upload bundle name. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
