Hi Andy,
The problem is you are signing the pkg but building it from an unsigned
> app-image.
>
> If you are building in two phases (app-image, then installer package) you
> need the --mac-sign option on both phases.
>
Thank you very much. It resolved the problem (I wasn't aware that
--mac-sign op
OK - took me a while to see what you are doing.
The problem is you are signing the pkg but building it from an unsigned
app-image.
If you are building in two phases (app-image, then installer package)
you need the --mac-sign option on both phases.
/Andy
On 8/3/2021 10:37 AM, Andy Herrick w
I was having problems notarizing anything yesterday, but fixed them today.
I can notarize my own test - but get failure when trying to notarize
your app as built from non-modular branch of
https://github.com/danielpeintner/Java11Test/
am looking into it ...
/Andy
On 8/2/2021 9:57 AM, Danie
Hi Andy,
> sorry - code looks for certificate key starting with: "Developer ID
> Application: " + in order to not
> have to put full user name in. I missed that that with null user name that
> causes it to look for anything starting with "Developer ID Application: "
> (same thing with "Develope
sorry - code looks for certificate key starting with: "Developer ID
Application: " + in order to not
have to put full user name in. I missed that that with null user name
that causes it to look for anything starting with "Developer ID
Application: " (same thing with "Developer ID Installer: "
Hi Andy,
Since I don't know your setup I did not put anything there.
'--mac-sign' is enough to use the defaults in my setup.
It looks for the signing keys installed on my machine that start with
"Developer
ID Application " similar to
'--mac-signing-key-user-name', 'Developer ID Application: '
et
The 'build.gradle' in this branch has --mac-signing-key-user-name
commented out.
installerOptions += [
'--mac-sign',
//
'--mac-s'SIGNING_KEY_USER_NAME'igning-key-user-name',
System.getenv('SIGNING_KEY_USER_NAME'),
// '--mac-signing-k