Timestamp server failing suddenly

Question

alectrocute OP

Created Aug ’21

Replies 5

Boosts 0

Views 2.7k

Participants 3

Hi 😢

When attempting to codesign, my command fails on CI this morning (however, identical build was succeeding last night). I'm assuming this is related to Apple's timestamp server based on similar posts on this forum in the past.

Error: Command failed: codesign --sign <redacted> --force --keychain /var/folders/z3/_825pg0s3jvf0hb_q8kzmg5h0000gn/T/<redacted>.keychain --timestamp --options runtime --entitlements config/mac_config/entitlements.mac.plist /Users/travis/build/<redacted>/dist_electron/mac-arm64/<redacted>.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Helpers/chrome_crashpad_handler
291
/Users/travis/build/<redacted>/<redacted>/dist_electron/mac-arm64/<redacted>.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Helpers/chrome_crashpad_handler: replacing existing signature
292
/Users/travis/build/<redacted>/<redacted>/dist_electron/mac-arm64/<redacted>.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Helpers/chrome_crashpad_handler: A timestamp was expected but was not found.

Please help, I really need to codesign my app! Thank you!

FB9493987 (Timestamp server issue)

Answered by alectrocute in 684651022

Apple has apparently solved the network connectivity issues. I am successfully signing builds again and have changed nothing. Apple – Is there any way to add documentation about this error and inform your third-party developers to "try again later"?

Boost

Answer 1

alectrocute OP

Aug ’21

Was recently suggested a workaround as per the Travis-CI support crew, will update my post here if this succeeds. Sharing it here in hopes it'll help another struggling developer.

--

Hey Alec,

Thanks for writing in and apologies for any inconvenience caused.

Could you please try a workaround using following commands:

before_install:
- wget https://www.apple.com/certificateauthority/AppleWWDRCAG3.cer
- sudo security import AppleWWDRCAG3.cer -k ~/Library/Keychains/login.keychain
- sudo security import AppleWWDRCAG3.cer -k /Library/Keychains/System.keychain

I hope this helps, please let us know if you need further assistance, we will be glad to help.

1

Answer 2

alectrocute OP

Aug ’21

The fix Travis-CI support suggest did not work. Still actively seeking a solution.

1

Answer 3

alectrocute OP

Aug ’21

Traceroute to timestamp.pki-apple.com.akadns.net:

traceroute to timestamp.pki-apple.com.akadns.net (17.32.213.129), 64 hops max, 52 byte packets
 1 pfsense.local.lan (192.168.1.1) 3.767 ms 1.747 ms 1.484 ms
 2 96.120.98.41 (96.120.98.41) 9.506 ms 11.737 ms 9.603 ms
 3 96.110.100.77 (96.110.100.77) 10.128 ms 10.976 ms 9.829 ms
 4 68.85.59.85 (68.85.59.85) 17.907 ms 15.248 ms 13.294 ms
 5 be-33933-cs03.miami.fl.ibone.comcast.net (96.110.45.89) 19.946 ms
  be-33943-cs04.miami.fl.ibone.comcast.net (96.110.45.93) 24.193 ms 22.513 ms
 6 be-3311-pe11.nota.fl.ibone.comcast.net (96.110.33.154) 22.159 ms
  be-3111-pe11.nota.fl.ibone.comcast.net (96.110.33.146) 20.331 ms
  be-3212-pe12.nota.fl.ibone.comcast.net (96.110.33.166) 18.828 ms
 7 50.208.233.38 (50.208.233.38) 22.797 ms
  50.208.233.30 (50.208.233.30) 21.533 ms
  50.208.233.38 (50.208.233.38) 25.629 ms
 8 17.0.14.79 (17.0.14.79) 44.012 ms
  17.0.14.73 (17.0.14.73) 44.230 ms
  17.0.14.79 (17.0.14.79) 44.369 ms
 9 17.0.14.78 (17.0.14.78) 46.318 ms
  17.0.14.72 (17.0.14.72) 43.001 ms 40.671 ms
10 17.0.14.51 (17.0.14.51) 45.219 ms
  17.0.14.45 (17.0.14.45) 45.287 ms
  17.0.14.47 (17.0.14.47) 52.996 ms
11 17.1.0.255 (17.1.0.255) 47.326 ms
  17.1.0.251 (17.1.0.251) 44.027 ms
  17.1.0.245 (17.1.0.245) 42.971 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 *

...and so on, for as long as I'll let it.

1

Answer 4

alectrocute OP

Aug ’21

Accepted Answer

Apple has apparently solved the network connectivity issues. I am successfully signing builds again and have changed nothing. Apple – Is there any way to add documentation about this error and inform your third-party developers to "try again later"?

1

Answer 5

DTS Engineer OP

Apple

Aug ’21

I’m glad to hear that got sorted out.

Is there any way to add documentation about this error and inform your third-party developers to "try again later"?

The best way to get that suggestion in front of the folks who maintain the documentation is to put it in an enhancement request.

Please post your bug number, just for the record.

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

0