errSecInternalComponent Issues

Question

Created 6d

Replies 2

Boosts 0

Participants 2

I have read the posted solution threads and am still stuck with solving this issue. I have created a python app that works perfect on my machine and I would like to distribute externally via .zip file.

I have created a certificate and downloaded it (G2 Sub-CA (Xcode 11.4.1 or later))

Next i have installed the Çert into the login keychain along with the Matching G2 Intermediate Cert (in system) and the proper Root Cert. However I am still not getting a proper chain when evaluating the developer certificate and I am at a loss at this point. I would love to pay someone to simply walk me through it if anyone has some time to solve this problem with me so I can run the notarytool and then distribute my application.

Thanks!

Answered by DTS Engineer in 826671022

I talked about this extensively in Resolving errSecInternalComponent errors during code signing. I’m not sure if that was “the posted solution” you’re referring too. It’d help you if you included more details in your post, like links to things you’ve tried, your OS version, and so on. See Quinn’s Top Ten DevForums Tips for lots of advice on that front.

My general advice for this — well, for debugging any problem really — is to constrain your environment. Install a ‘fresh’ copy of macOS and repeat your test there. Ideally this would be in a VM, where you can restore to your fresh snapshot between each test. You should be able to get code signing to work in that environment. If not, that’s something I can help you investigate.

And once you do get that to work, that suggests that whatever’s causing this problem is related to the state of your main work Mac.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

5d

Recommended

I talked about this extensively in Resolving errSecInternalComponent errors during code signing. I’m not sure if that was “the posted solution” you’re referring too. It’d help you if you included more details in your post, like links to things you’ve tried, your OS version, and so on. See Quinn’s Top Ten DevForums Tips for lots of advice on that front.

My general advice for this — well, for debugging any problem really — is to constrain your environment. Install a ‘fresh’ copy of macOS and repeat your test there. Ideally this would be in a VM, where you can restore to your fresh snapshot between each test. You should be able to get code signing to work in that environment. If not, that’s something I can help you investigate.

And once you do get that to work, that suggests that whatever’s causing this problem is related to the state of your main work Mac.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

DTS Engineer OP

Apple

4d

So wrapping my head around some of this has been a learning experience.

Yeah, I don’t think anyway has ever claimed that this was easy )-:

Anyway, if you have follow-up questions, feel free to ask them here. Two things to note:

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits.
Feel free to tag me in your reply, using the traditional @ syntax. I’ll probably see it anyway, but tagging me never hurts (-:

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0