Re: Customizing the Notarization Workflow fails

2020-05-04 Thread St John, David R via Cocoa-dev
Setting automatic code signing to Off and "Code Sign style" = Manual just means you have control over the certificate, developer team, etc. not that Xcode won't sign your product. There used to be a "Don't Code Sign" option which did as advertised but it hasn't been an option in a Xcode

Re: Customizing the Notarization Workflow fails

2020-05-04 Thread João Varela via Cocoa-dev
> On 3 May 2020, at 21:31, Gabriel Zachmann wrote: > > Thanks a million to everybody for responding to my question! > > > I have been following Joao's instructions at > > >

Re: Customizing the Notarization Workflow fails

2020-05-03 Thread Gabriel Zachmann via Cocoa-dev
Thanks a million to everybody for responding to my question! I have been following Joao's instructions at https://stackoverflow.com/questions/53101626/how-to-notarize-an-app-bundle-containing-helpers-embedded-in-it/56799591#56799591

Re: Customizing the Notarization Workflow fails

2020-04-26 Thread João Varela via Cocoa-dev
Hi, Gabriel As far as I know, if it is not a standard application package, you cannot use the organizer to archive properly a package and then send it to the notarizing server. I struggled with it for a long time, more than a year, until Apple gave us the proper documentation in WWDC 2019 for

Re: Customizing the Notarization Workflow fails

2020-04-25 Thread Jerome Krinock via Cocoa-dev
After similar frustration with Xcode’s notarization, I scripted notarization using command-line tools, integrating it into my existing build/archive/codesign/ship script. This post explains how to script the notarization, and in the last answer someone open-sourced their script:

Re: Customizing the Notarization Workflow fails

2020-04-25 Thread John Joyce via Cocoa-dev
The life hack for this is to have a Run Script Build Phase that just lists out the build variables and their values. Then you look them up in the help menu to confirm what they mean. > On Apr 26, 2020, at 10:29, Jack Brindle via Cocoa-dev > wrote: > > Before someone reminds me, be sure to

Re: Customizing the Notarization Workflow fails

2020-04-25 Thread Jack Brindle via Cocoa-dev
Before someone reminds me, be sure to use the Xcode global variables for all this work. You will find the build directory in one of the variables (it’s Saturday - I don’t remember right now, so I hope someone bales me out again). You can then use that var in the Notarization script to get your

Re: Customizing the Notarization Workflow fails

2020-04-25 Thread Jack Brindle via Cocoa-dev
It seems like it would be easier to find the Build directory’s releases folder and the find the built product somewhere inside. It’s relation to the Build directory won’t change from build to build. Once you find that, just Notarize it in place. You need to make sure that it is already

Re: Customizing the Notarization Workflow fails

2020-04-25 Thread Gabriel Zachmann via Cocoa-dev
Thanks a lot for your response. > I’m not sure how you would script the export, but if you go to menu option > Window -> Organizer, you can see your archives. Yes, I can see them. But when I do "Show in Finder", then "Show package contents", they contain nothing (except for an empty Products

Re: Customizing the Notarization Workflow fails

2020-04-25 Thread James Crate via Cocoa-dev
On Apr 25, 2020, at 10:12 AM, Gabriel Zachmann via Cocoa-dev wrote: > > I am trying to follow these instructions: > > https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/customizing_the_notarization_workflow?language=objc > > However, I can't even

Customizing the Notarization Workflow fails

2020-04-25 Thread Gabriel Zachmann via Cocoa-dev
I am trying to follow these instructions: https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/customizing_the_notarization_workflow?language=objc However, I can't even achieve the first step ("Export a Package for Notarization"). As per the