Post

Replies

Boosts

Views

Activity

How to find and delete a revoked certificate
Using xcode 12.2, on a new Mac, compiling an app with a fat binary, I want to submit it to the apple store. I create an Archive and when I ask xcode to "Validate App", I select that xcode should "Automatic manage signing", with a Certificate: Apple Distribution (Expires 15/11/21) and I finally receive this error message: App Store Connect Operation Error Certificate Revoked. The signing certificate "C=US, O=XXXXXXXX, OU=XXXXXXX, CN=3rd Party Mac Developer Installer: XXXXXXX (XXXXXX), UID=XXXXXXXX" with serial number XXXXXXXXXXXXXXXX used to sign StarMessage screensaver.pkg has been revoked. Learn more (https://help.apple.com/xcode/mac/current/#/dev154b28f09). This message is not helpful at all because: The serial number is not listed in the xcode/manage certificate screen, nor in keychain, nor in the developer.apple.com. It does not mention the expiry date or the issue date of the cert to give it as a hint for me to find it between the other certificates. The naming of the apple certificates is a puzzle itself, and the name as mentioned in this message does not match any of the names of the certificates in the 3 mentioned areas. All certs in the xcode/manage certificate screen, in the keychain, and in the developer.apple.com look valid and have not expired. So, how can I find this problematic certificate and delete it? I tried https://stackoverflow.com/questions/36689116/certificate-has-either-expired-or-has-been-revoked/53925890#53925890 with no luck. Thanks!
2
0
3.1k
Nov ’20
NSHighResolutionCapable ignored in the case of .saver bundles.
Hi, I have a screensaver (called "StarMessage") that is build both as an app distributed via the Apple store and as a . native screensaver (.saver) - https://github.com/starmessage/StarMessage-screensaver/tree/master/Apple%20MacOS%20screensaver%20download distributed from my website. When the user selects a tiled image background, the screensaver drawing becomes too slow on retina monitors. By adding NSHighResolutionCapable = false at the app edition the drawing speed is back to normal. But in the .saver edition this setting is ignored. Probably because it is the screensaverEngine.app that is examined by MacOS and it does not have that setting. My questions are: is there a way for this setting to also work on .saver bundles as it does for .app bundles? is there an alternative way to achieve programmatically what NSHighResolutionCapable does? The drawing is done with very simple native functions (not openGl, no metal) using a very simple cross platform library: https://github.com/starmessage/cpcc At the moment, I do not want to redo the drawing code although I understand that would be the best solution. I hope there is a solution for me. thanks
1
0
1.1k
Oct ’20