errSecInternalComponent error with Developer ID Application certificate G2 Sub-CA

[resonant]

@dannytaurus said in errSecInternalComponent error with Developer ID Application certificate G2 Sub-CA:

@resonant Did you do the 'intermediate certificate' thing? I recall having to add something like that to keychain.

No I didn't? Does yours work like that? There was no such need before.

[dannytaurus]

@resonant I think that was part of the change in the new 2031 method. You install an intermediate cert that actually issues your cert.

My Keychain, filtered for 'developer':

There's an older 2027 entry at the bottom, but the top ones are for my working cert.

[dannytaurus]

@resonant Claude recommends running these commands to make sure everything is working:

$ xcodebuild -version
Xcode 26.1.1
Build version 17B100
$ sw_vers
ProductName:		macOS
ProductVersion:		15.7.4
BuildVersion:		24G517
$ security find-identity -v -p codesigning
  1) XXXXXXXXXXXXXXXX "Developer ID Application: Daniel Weaver (XXXXX)"
     1 valid identities found

[resonant]

@dannytaurus

Thank you for the tip! Which of these is the "intermediate thing" option?

[dannytaurus]

@resonant You need the bottom two, but I'm not sure which is first. Claude should be able to guide you through it.

[dannytaurus]

@resonant Claude says:

For VST3, AU, AAX, standalone apps, and notarization, you create Developer ID Application first.

The normal sequence is:

1. Developer ID Application
   * Used to sign:
   * .app
   * .component (AU)
   * .vst3
   * .aaxplugin
   * frameworks, dylibs, helpers, etc.
   * Required for notarization.
2. Developer ID Installer (optional)
   * Only needed if you’re distributing a signed .pkg installer.
   * Signs the package itself, not the plugin inside it.

[David Healey]

@dannytaurus said in errSecInternalComponent error with Developer ID Application certificate G2 Sub-CA:

You need the bottom two, but I'm not sure which is first.

Order you create them doesn't matter. One is for signing plugins, the other is for the installer.

[dannytaurus]

@David-Healey You don't even need the Installer one if you're not creating installers.

All you need is the Application one if you're just signing the plugins themselves.

[David Healey]

@resonant Just plugging my wares, I have a workshop that will walk you through the process: https://audiodevschool.com/courses/packaging-for-macos/

[dannytaurus]

@David-Healey Very excellent wares they are too