A timestamp was expected but was not found

Code Signing General
arun27.a@gmail.com OP
Created Jul ’20
Replies 35
Boosts 0
Views 12k
Participants 17
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 and 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.

Answered by DTS Engineer in 622559022
Based on some great bug reports filed by folks on this thread, the team responsible for the timestamp server was able to track down and fix what they believe is the root cause of this problem. So, everything should be all good now (-:

If you see this problem crop up again (and we’re still investigating why it wasn’t detected by our own internal systems) please file a bug report and then post your bug number here.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"
Replies  35
Boosts  0
Views  12k
Participants  17
YakovN OP
Jul ’21

Faced the same problem. Nothing changed on our CI machine, but the build stopped working with codesign "a timestamp was expected but was not found" error. wrote to the feedback assistant - FB9288985

call traceroute timestamp.apple.com gives:

traceroute to timestamp.pki-apple.com.akadns.net (17.179.249.1), 64 hops max, 52 byte packets
 1  188.128.25.25 (188.128.25.25)  0.718 ms  0.360 ms  0.547 ms
 2  5.143.233.1 (5.143.233.1)  1.541 ms  1.637 ms  1.541 ms
 3  87.226.174.241 (87.226.174.241)  1.918 ms  1.715 ms  1.627 ms
 4  * * 188.128.126.81 (188.128.126.81)  43.306 ms
 5  17.1.168.136 (17.1.168.136)  48.196 ms  36.598 ms  57.129 ms
 6  17.0.12.112 (17.0.12.112)  228.237 ms  218.270 ms
    17.0.12.116 (17.0.12.116)  222.642 ms
 7  17.1.3.243 (17.1.3.243)  218.001 ms  210.820 ms  219.386 ms
 8  17.1.3.240 (17.1.3.240)  223.942 ms
    17.1.3.242 (17.1.3.242)  211.452 ms  219.917 ms
 9  17.1.2.171 (17.1.2.171)  230.444 ms
    17.1.2.179 (17.1.2.179)  219.296 ms  226.349 ms
10  17.1.2.176 (17.1.2.176)  219.132 ms  212.270 ms  219.311 ms
11  17.1.0.119 (17.1.0.119)  220.040 ms
    17.1.0.113 (17.1.0.113)  211.403 ms  218.593 ms
12  17.0.8.35 (17.0.8.35)  236.001 ms  210.848 ms  224.461 ms
13  * * *
14  17.0.13.205 (17.0.13.205)  225.599 ms
    17.1.1.35 (17.1.1.35)  230.321 ms
    17.0.13.205 (17.0.13.205)  212.251 ms
15  * * *
16  * * *
17  * * *
1
DRazvarov OP
Jul ’21

Today faced this problem on CI machine. Where is no changes in configuration. From time to time codesign failed with "a timestamp was expected but was not found". Wrote request in feedback assistant FB9290141.

1
mmarczell OP
Jul ’21

Experiencing this in Hungary again, too. As before, not on every machine.

1
Akira.H OP
Jul ’21

I Faced same problem from few days ago in Japan. I wrote to feedback assistant FB9282952.

1
alectrocute OP
Aug ’21

I'm actively facing this issue and cannot codesign any of my builds on CI. This is a major problem for us.

https://developer.apple.com/forums/thread/687788

Created a ticket in Feedback Assistant, FB9493987.

1
alectrocute OP
Aug ’21

Paging @eskimo? 🙏

1
DTS Engineer OP
Apple
Aug ’21

Created a ticket in Feedback Assistant, FB9493987.

I’ll respond on your new thread.

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

0
OneTwoThree OP
Jul ’22

Hi, 

This issue is happening from this week. It works sometimes. Both Codesign and productsign commands are failing. I have created FB10804197. It is working from our office in California. Could you please help. 

regards 

Prema Kumar 

0
DTS Engineer OP
Apple
Jul ’22

It is working from our office in California.

Given your other recent thread, I suspect that this is more to do with the network setup in your non-California office than the timestamp service itself.

The timestamp service is an HTTP server available at timestamp.apple.com. I recommend that you try running some standard network diagnostics in the office where you’re having problems. For example:

% curl http://timestamp.apple.com
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>Apple</center>
</body>
</html>

The 302 response means that the request made it through to the origin server.

And:

% telnet timestamp.apple.com 80
Trying 17.32.213.129...
Connected to timestamp.pki-apple.com.akadns.net.
Escape character is '^]'.
^]
telnet> q
Connection closed.

The telnet tool is no longer built-in to macOS but you can either install it yourself use use nc.

And:

% host timestamp.apple.com
timestamp.apple.com is an alias for timestamp.pki-apple.com.akadns.net.
timestamp.pki-apple.com.akadns.net has address 17.32.213.129

And:

% traceroute timestamp.apple.com
traceroute to timestamp.pki-apple.com.akadns.net (17.32.213.129), 64 hops max, 52 byte packets
…

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

0
OneTwoThree OP
Jul ’22

Hi Quinn,

Thank you for the support. I have tried the commands and updated the ticket. It takes more than one minute to establish the connection. Sometime the connection gets timeout as well.

regards Prema Kumar

0
DTS Engineer OP
Apple
Jul ’22

I have tried the commands and updated the ticket.

Your ticket with us (FB10804197)? Or your ticket with your own network team?

It takes more than one minute to establish the connection.

Honestly, this sounds like another instance of a problem with your firewall. If one of your colleagues in the same region as your non-California office does this from their home network, or from a WWAN network, do you still see the same delay?

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

0
OneTwoThree OP
Jul ’22

Hi Quinn,

I have updated in the FB10804197. traceroute command details also updated.

I will give the other information soon.

regards

Prema Kumar

0
OneTwoThree OP
Jul ’22

Hi Quinn,

We bypassed the firewall as well. Still getting the issue. Could you please try the following?

traceroute from 17.179.249.1 to 103.36.149.1 and 17.179.249.1 to 103.36.149.2

regards

Prema Kumar

0
DTS Engineer OP
Apple
Jul ’22

Could you please try the following?

My running these traceroutes is unlikely to help because my packets will take a completely different route that yours.

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

0
OneTwoThree OP
Jul ’22

Hi Quinn,

Thank you for your reply.

Could you please let us know why the requests are failing when they are originated from IP 103.36.149.7?

Many thanks in advance.

Regards

Prema Kumar

0
A timestamp was expected but was not found
First post date Last post date
 
 
Q