>>
>> 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. Ju
> 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
> 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 developme
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
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
