> > As for the App Store version, I’m not sure how I can distribute that > internally for testing - signing with the Developer ID doesn’t seem to be > right, but it’s unclear what other options I have. > > —Graham >
That’s what the Mac Development ID is for. That’s embedded into the provisioning profiles for development with a list of Mac devices in it, so you can run your app on those machines. Then you submit it to the store with your Mac App Distribution signing identity which Apple then re-signs with their own later. I’ve never quite understood why there’s a separate Installer Distribution Identity but there is; and finally you have your Developer ID which really just signs apps as being traceably from you but allows limited access to any of the features like iCloud etc. So if you don’t need any of the entitlements you can only get with a real sandboxed, signed, store (or Mac Development) app, then you could just sign with your Developer ID, or not bother to sign it at all. If you do need them, add the machines you want to run on to the account and generate a provisioning profile with them embedded, or let Xcode do that for you with one of its magic team provisioning profiles. _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
