A project that usually signed without issues will now stall in AppWrapper, telling me the signature is invalid, hardened runtime is not enabled and no timestamps are on the files. Which should be, and wrapping itself completes without errors (though some warnings).
Is it just me and this project or are there any hiccups on Apple’s services?
From the DMG part of the log:
• [ERROR] The signature of the binary is invalid.
• [ERROR] The signature does not include a secure timestamp.
• [ERROR] The executable does not have the hardened runtime enabled.
• [ERROR] The signature of the binary is invalid.
• [ERROR] The signature does not include a secure timestamp.
• [ERROR] The executable does not have the hardened runtime enabled.
Sorry – too early. It looked like adding some more notarisation exceptions would help. It did not.
If I try to run AppWrapper for a second time, it will fail due to permission issues …?
I’ve had the exact same issues at about the same time as you, so we now both know it was something on Apple’s servers.
I did check Internet status of a few websites, including Apple’s/Apple status page, and indeed some were completely unreachable (not for just me) and others were hard to reach (some worked, though).
There were some issues, indeed. Glad I may try again and it’s not my software that got corrupt.
You’re welcome.
I was speaking of the past because the websites I had checked eventually came to life again, after several minutes, but I hadn’t attempted signing again (I was busy for other things).
So I just checked now, and I can indeed sign again.
Now works for me too again.
As it turned out, it were two issues instead of only the API outage. I had updated a console helper app for this project and there was a build log in the folder which ruined code signing.
Phew. I was already considering mild panic as a healthy response to this situation.
