codesign fails due to timestamp issue - server probably down

I'm signing using "Developer ID Application" and it suddenly started failing due to the following reason A timestamp was expected but was not found.. from the logs it looks like a failure to connect Apple's dedicated server. Perhaps there's a way to verify this theory, or get another timestamp server to be set in --timestamp option?

thanks

2023-04-24 15:53:38.977560+0300 0x2e29ef5  Error       0x0                  696    0    XPCTimeStampingService: (CFNetwork) NSURLConnection finished with error - code -1001
2023-04-24 15:53:38.977753+0300 0x2e29ef5  Default     0x0                  696    0    XPCTimeStampingService: (CFNetwork) [com.apple.CFNetwork:Summary] Task <42F5893A-941A-4293-BB14-F75C42363836>.<0> summary for task failure {transaction_duration_ms=15792, response_status=-1, connection=817, reused=1, request_start_ms=0, request_duration_ms=0, response_start_ms=0, response_duration_ms=0, request_bytes=0, response_bytes=0, cache_hit=false}

or get another timestamp server

That won’t help because the purpose of the timestamp is to provide a secure way for the system to determine when your code was signed, and for that to work you must use the Apple timestamp service.

Regarding your main issue, see this post.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

codesign fails due to timestamp issue - server probably down
 
 
Q