> On 1 Jan 2016, at 09:05, Graham Cox <graham....@bigpond.com> wrote: > > >> On 1 Jan 2016, at 11:54 AM, Roland King <r...@rols.org> wrote: >> >> Developer ID’ doesn’t sound right. Developer ID is for signing apps for >> non-mac-store distribution, > > > That’s exactly what I want to do. > > >> If you want to distribute a test copy of the app you need to sign it with >> the Mac developer certificate using a provisioning profile which contains >> the device which is going to run it. > > > I have no idea what device is going to run it. The app is a private copy for > testing, but by others, not by me. I usually handle this by simply signing it > with a Developer ID. That stops the testers getting the Gatekeeper warning, > but otherwise doesn’t put any special requirements on them. They can also > verify that the app is signed by the expected developer. > > >> The Mac Distribution certificate is for signing apps to send to the App >> Store where they get re-signed for distribution to the world. > > > At the stage the app isn’t destined for the App Store. > > >> Didn’t know that the thing would crash however > > Yes, I’ve never seen this behaviour before either. I don’t really get it - > the iCloud signatures appear to match the Developer ID. Perhaps iCloud Drive > is simply unavailable to non App Store apps? If so it’s not very friendly > about saying so, and also makes it difficult to test the functionality. The > app will go in the App Store eventually, but our testing procedures are far > smoother at this stage (beta) without bringing that into it. > > —Graham > >
See if you can make head or tail of this table https://developer.apple.com/library/mac/documentation/IDEs/Conceptual/AppDistributionGuide/SupportedCapabilities/SupportedCapabilities.html#//apple_ref/doc/uid/TP40012582-CH38-SW1 <https://developer.apple.com/library/mac/documentation/IDEs/Conceptual/AppDistributionGuide/SupportedCapabilities/SupportedCapabilities.html#//apple_ref/doc/uid/TP40012582-CH38-SW1> That tells you what you can and can’t do with different types of ID. However I don’t understand the difference between the filled an unfilled circles. eg take iCloud Documents row under the ‘Mac Developer ID’ certificate, which is probably what you want. It’s there, so it should be available. The circle is filled however and the note at the bottom says Requires an Apple ID associated with an Apple Developer Program membership. For Mac apps, the signing identity must be set to Mac App Store. But hold on, if the signing identity is set to Mac App Store, why is it in a column where the signing identity is Mac Developer ID? I’ve read it several times now and I’m still confused. Possible that you select Mac App Store in one place and Mac Developer ID in a different place and somehow that combination works to do what you want. I also thought that the non developer program support IDs which were introduced in Xcode 7, meaning you didn’t have to buy the membership every year, didn’t have access to iCloud however looking at the lefthand column of that table, the icons are unfilled which to me would mean I can use iCloud using a ‘free’ account, for my own purposes. And finally see the note at the very bottom telling you how to use iCloud Drive in 10.11 without needing an iCloud entitlement at all. I think this is now officially more complicated than it needed to be. _______________________________________________ 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
