No, I don't have specific concern about this, but just noticed this when investigating the issue reported in FB15488021.
Pengjie
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
The feedback has been submitted with bug number FB15488021
Registering the menu bar app as login item through JamfNow has the similar behavior: uid=-1
This error appears only when running with "sudo launchctl setenv", without "sudo" it works well.
I confirm that this issue still exists on macOS Sonoma.
Since directly deleting the hosting App is the suggested approach to uninstall a system extension, Apple should fix this issue.
Has anybody opened a ticket with Apple?
@eskimo
Thanks for detailed explanation.
I solved the issue in this way: Instead of static linking with MyClass in the shared library, the shared library gets the referece of MyClass which is initiated in the loader.
I had the very similar issue on our build machine with TeamCity installed. The build and notary script even works smoothly when it is being called manually on the build machine. But when the building process is triggered automatically, such as a nightly build, it failes with:
Info [KEYCHAIN] No Keychain password item found for: AC_PASSWORD
The solution for me was that the keychain profile has to be stored in the login keychain, but not in the default iCloud/Login Items keychain when running the comand "notarytool store-credentials", otherwise the keychain profile, no matter app-specific-password or App Store Connect Key won't be listed by 'security find-generic-password -l '. I think there must be a bug related to "notarytool store-credentials" and "security find-generic-password -l".