Re: Distributing Mac App to Registered Devices
>> >> Notarize your beta builds, just like you should be doing with your release >> builds. > > Yes, that is what I do now. However when upgrading to Xcode 12 it wants to > change the debug and release configuration to use development signing. > Notarized builds are reserved for archiving. Just saying that AFAIK, you can build archive version with full debug symbols enabled. Best regards, Gabriel smime.p7s Description: S/MIME cryptographic signature ___ 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
Re: Distributing Mac App to Registered Devices
> On 23 Jun 2021, at 12:22 pm, Richard Charles via Cocoa-dev > wrote: > > Yes, that is what I do now. However when upgrading to Xcode 12 it wants to > change the debug and release configuration to use development signing. > Notarized builds are reserved for archiving. Just saying that Apple is > steering everyone in that direction. You ought to build your test versions via the archiving method, just like you do your public release versions. > Apple's answer to the problem is registering devices in your developer > account. Except is does not work with mac devices. I don't think that's quite right. Developer-provisioned builds are really only useful to developers (in particular, they allow a debugger to be attached, which is immaterial to end users). -b ___ 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
Re: Distributing Mac App to Registered Devices
> On Jun 23, 2021, at 12:49 PM, James Walker via Cocoa-dev > wrote: > > Notarize your beta builds, just like you should be doing with your release > builds. Yes, that is what I do now. However when upgrading to Xcode 12 it wants to change the debug and release configuration to use development signing. Notarized builds are reserved for archiving. Just saying that Apple is steering everyone in that direction. Apple's answer to the problem is registering devices in your developer account. Except is does not work with mac devices. --Richard Charles ___ 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
Re: Distributing Mac App to Registered Devices
On 6/23/21 9:33 AM, Richard Charles via Cocoa-dev wrote: How do you distribute software (not on app store) to Mac beta testers and not be presented with a malicious software warning? Notarize your beta builds, just like you should be doing with your release builds. When upgrading a project to Xcode 12.5 it wants to change the debug and release configuration to use development signing. However when a beta tester downloads and opens a debug or release configuration version of the app with development signing they are presented with a malicious software warning. One way to open the app anyway is to go to System Preferences > Security & Privacy and click Open Anyway. Another way is for the developer to register the device UDID of the beta tester’s machine. However it does not work. The registered machine is still presented with a malicious software warning when opening the app. So has anyone gotten this to work? https://developer.apple.com/documentation/xcode/distributing-your-app-to-registered-devices --Richard Charles ___ 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
Distributing Mac App to Registered Devices
How do you distribute software (not on app store) to Mac beta testers and not be presented with a malicious software warning? When upgrading a project to Xcode 12.5 it wants to change the debug and release configuration to use development signing. However when a beta tester downloads and opens a debug or release configuration version of the app with development signing they are presented with a malicious software warning. One way to open the app anyway is to go to System Preferences > Security & Privacy and click Open Anyway. Another way is for the developer to register the device UDID of the beta tester’s machine. However it does not work. The registered machine is still presented with a malicious software warning when opening the app. So has anyone gotten this to work? https://developer.apple.com/documentation/xcode/distributing-your-app-to-registered-devices --Richard Charles ___ 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
