Posts

Post not yet marked as solved
7 Replies
0 Views
Thanks. I use the Xcode managed certificates. Then I think you must be right. Very glad with your help. You are a good man. Really appreciate with you.
Post not yet marked as solved
7 Replies
0 Views
Thanks. Your method works, and now Developer ID certificate is valid and green. However, the WWDR R3 is still wrong. I have installed  Apple Root CA - G3 Root , but not worked.
Post not yet marked as solved
7 Replies
0 Views
Thanks for your help. My MacOS is 12.3, and Xcode is 13.4.1 . Follow your guide, I right-click and evaluate my certificate, and got the pictures as below. Seems not same as you point out.
Post not yet marked as solved
1 Replies
0 Views
Seems nobody replies to me. Up to this thread.
Post not yet marked as solved
2 Replies
0 Views
Anyone can give me some help to pass the notarization service? Below is my codesign command for the bundle, and the --deep parameter affects the signature of the main executable file. sudo codesign --force --deep --timestamp --options=runtime -s "Developer ID Application: Some Company (XXXXXX)" ./XXXX.app And I also tried to codesign the single executable file yyyy directly, but the error remained. I need more info to move forward. Or somebody can tell me how to connect with Apple Notarization Service Team. Their notarization response cannot point out what blocks my executable file.