validateAuthorizationArgs doesn't work when using `keychain` and `keychainProfile`
See original GitHub issueThe validateAuthorizationArgs
check is now really the validateLegacyAuthorizationArgs
check from the electron-notarize
package.
https://github.com/electron/electron-packager/blob/bde6031985cc83d25ffd78532e1ce3baa88dd79d/src/mac.js#L419-L425
This means that using the keychain-profile method of authentication causes an error:
Packaging ApplicationWARNING: Failed validation, notarization will not run: No authentication properties provided (e.g. appleId, appleApiKey)
Forge -> Packager -> Notarizer config:
"osxNotarize": {
"keychain": "~/Library/Keychains/login.keychain-db",
"keychainProfile": "AC_PASSWORD"
},
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
If your Mac keeps asking for your keychain password
In the Keychain Access app on your Mac, click “login” in the Keychains list. Choose Edit > Change Settings for Keychain “login.” Select...
Read more >How to Resolve Mac OS X Keychain Problems
Click General, then click Reset My Default Keychain. Authenticate with your account login password. Quit Keychain Access. Restart your computer.
Read more >10 Common Keychain Problems and Solutions on macOS 10.15
Problem #1: Mac OS Asking for Keychain Password Repeatedly · 1. Go to Applications/Utilities and launch the Keychain Access app. · 2. Click...
Read more >missing private key in the distribution certificate on keychain
With the developer profile, everything works good, but when I installed the cert and the provisioning profile, I did not see the distribution...
Read more >How to fix the 'Accountsd wants to use the login keychain' alert
This is the Mac's Keychain Access app working in the background, which is where passwords are kept. The accountsd Mac framework is how...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It can’t support both modes without knowing the “tool” prop passed in otherwise it can allow invalid auth config for the wrong tool.
I can export both and packager can call them conditionally? Or export a wrapper that calls it conditionally.
But IMO the argument validation should be left to this package, what can we put on the error so you know it’s a validation error?
Running into this too