A timestamp was expected but was not found

Question

beamdev OP

Created Apr ’22

Replies 3

Boosts 0

Views 1.1k

Participants 2

Hello,

Since few days we cannot sign our application due to CodeSignin error: A timestamp was expected but was not found

I have opened FB9997275

I tried to traceroute timestamp.apple.com but it never ends

 1  51.159.121.1 (51.159.121.1)  1.214 ms  0.551 ms  0.459 ms
 2  51.158.2.13 (51.158.2.13)  1.061 ms
    51.158.2.11 (51.158.2.11)  0.968 ms  0.728 ms
 3  51.158.2.32 (51.158.2.32)  0.696 ms
    51.158.2.34 (51.158.2.34)  0.874 ms
    51.158.2.36 (51.158.2.36)  0.716 ms
 4  51.158.2.8 (51.158.2.8)  0.871 ms
    51.158.2.0 (51.158.2.0)  1.011 ms  0.851 ms
 5  apple-1.par.franceix.net (37.49.237.176)  1.258 ms  1.386 ms  1.113 ms
 6  17.0.11.136 (17.0.11.136)  95.672 ms  96.637 ms
    17.0.11.130 (17.0.11.130)  99.582 ms
 7  17.0.15.136 (17.0.15.136)  96.593 ms
    17.0.15.134 (17.0.15.134)  96.727 ms
    17.0.15.136 (17.0.15.136)  96.523 ms
 8  17.0.15.177 (17.0.15.177)  95.605 ms
    17.0.15.175 (17.0.15.175)  96.647 ms  95.433 ms
 9  17.0.15.41 (17.0.15.41)  96.356 ms  95.740 ms *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
...

I also tried to nc -v timestamp.apple.com 80 but it succeeds: Connection to timestamp.apple.com port 80 [tcp/http] succeeded!

Anything we can do on our side ? Nothing changes since this error happened.

Regards

Boost

Answer 1

DTS Engineer OP

Apple

Apr ’22

I’ve not seen widespread reports of timestamp service problems in recent days. For general advice about this, see this post.

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

0

Answer 2

beamdev OP

Apr ’22

Thanks for your answer. I also tried in my local computer and not in the CI and I still have issue with trace route to timestamp service:

traceroute to timestamp.pki-apple.com.akadns.net (17.32.213.129), 64 hops max, 52 byte packets
 1 box (192.168.1.1) 4.968 ms 6.672 ms 13.364 ms
 2 1.112.95.92.rev.sfr.net (92.95.112.1) 11.883 ms 9.336 ms 9.585 ms
 3 46.164.96.84.rev.sfr.net (84.96.164.46) 10.132 ms 10.836 ms 15.264 ms
 4 54.164.96.84.rev.sfr.net (84.96.164.54) 10.895 ms 16.320 ms 17.808 ms
 5 186.144.6.194.rev.sfr.net (194.6.144.186) 25.407 ms 25.105 ms 27.131 ms
 6 186.144.6.194.rev.sfr.net (194.6.144.186) 233.782 ms 25.528 ms 24.219 ms
 7 17.1.105.0 (17.1.105.0) 22.432 ms 21.230 ms 31.693 ms
 8 17.0.11.136 (17.0.11.136) 141.589 ms 114.517 ms
  17.0.11.130 (17.0.11.130) 119.215 ms
 9 17.0.15.134 (17.0.15.134) 111.725 ms
  17.0.15.136 (17.0.15.136) 112.120 ms 112.272 ms
10 17.0.15.175 (17.0.15.175) 122.841 ms
  17.0.15.177 (17.0.15.177) 114.828 ms 111.049 ms
11 * 17.0.15.41 (17.0.15.41) 116.556 ms 113.311 ms
12 17.1.0.255 (17.1.0.255) 119.837 ms * 118.071 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 *

How can it be explained ?

0

Answer 3

DTS Engineer OP

Apple

Apr ’22

I also tried in my local computer

Your local computer on the same network? Or your local computer on a completely different network.

FYI, I don’t put a lot of stock in traceroute. It’s useful in some circumstances but there are lots of reasons for it to produce weird results on the modern Internet. You’re other test, running nc against the service, is the acid test IMO. Consider this:

% nc -v timestamp.apple.com 80
Connection to timestamp.apple.com port 80 [tcp/http] succeeded!
GET /
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>Apple</center>
</body>
</html>

Here’s I’ve sent the service a completely bogus request (an HTTP 1.0-style GET of /) and it’s rightly rejected that. However, that rejection is all I need to show that my communication path with the service is working correctly.

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

0