A timestamp was expected but was not found

Question

Created 23h

Replies 2

Boosts 0

Participants 2

We are facing following message "A timestamp was expected but was not found" during codesign for following .dylib and .pkg and it cause notarization process failed.

We are facing this issue for last 3 days.

we have access for timestamp.apple.com and 17.0.0.0/8 and we didn't change firewall settings. We are facing this issue randomly and not for all time(scenario is 3:1).

We tried the below command to sign the package,

codesign --verbose --deep --force --timestamp --options=runtime --sign "<CODE SIGN IDENTITY>" <TO BE SIGNED PACAKGE>

Kindly let us know how to fix this probelm.

traceroute timestamp.apple.com

traceroute to timestamp.v.aaplimg.com (17.157.80.35), 64 hops max, 52 byte packets

....

10 17.0.9.19 (17.0.9.19) 185.693 ms 17.0.9.17 (17.0.9.17) 180.932 ms 189.060 ms

11 * * *

12 17.0.17.141 (17.0.17.141) 191.513 ms * 17.0.17.137 (17.0.17.137) 183.086 ms

13 * * *

14 * * *

Boost

Answer 1

DTS Engineer OP

Apple

22h

Run this in the same environment in which you’re running codesign:

% curl -D /dev/stderr http://timestamp.apple.com

What do you get back? Does it yield the same level of inconsistency, that is, working sometimes and failing others?

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

1

Answer 2

Samuellllll OP

4h

I tried to run the command, its output is below:

curl -D /dev/stderr http://timestamp.apple.com
HTTP/1.1 302 Moved Temporarily

Server: Apple

Date: Wed, 16 Oct 2024 03:41:14 GMT

Content-Type: text/html

Content-Length: 138

Connection: keep-alive

Location: https://www.apple.com/certificateauthority/

Host: timestamp.apple.com

X-Content-Type-Options: nosniff

X-Frame-Options: SAMEORIGIN

X-XSS-Protection: 1; mode=block



<html>

<head><title>302 Found</title></head>

<body>

<center><h1>302 Found</h1></center>

<hr><center>Apple</center>

</body>

</html>

but it also stuck with no output after running the command, like 3 out of 5 times.

what's the problem?

0