Git commit failure (Mojave): client is not Apple-signed
cstarkjp opened this issue · 0 comments
Prerequisites
- [ X] Put an X between the brackets on this line if you have done all of the following:
- Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
- Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
- Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
- Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
- Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
Git commit fails, i.e., does nothing, on MacOS Mojave.
Console shows securityd code requirement check failed (-67050), client is not Apple-signed error is generated by this action.
Execution with git commit -m 'msg' or git commit -S -m 'msg' from a shell command line works fine.
Atom application is run by "right-clicking". Security & Privacy settings Allow apps downloaded from App store and identified developers
Steps to Reproduce
- Stage an edited file
- Press "Commit to master" or hit cmd-enter
Expected behavior:
Should execute a git commit -m 'msg' or git commit -S -m 'msg'
Actual behavior:
No action; client not Apple-signed error generated on console
Reproduces how often:
Always
Versions
Atom version: 1.48.0 x64
MacOS version: 10.14.5 Mojave
Additional Information
Atom is a fresh install. GPG also. Signing error appears to have nothing to do with GPG in any case.
Git add (staging), pushing and fetching to Github work correctly from Atom. Only commit fails.
The git repo was freshly created.
This is not the first time this issue, or similar, has been reported, but the fixes (such as "right-clicking" to launch the application), refreshing GPG signing, etc have not worked.