segmentation fault codesign -s "Developer ID Application: Teamxxxxx"

Are you receiving a segmentation fault when you run your app, or when you try to code sign your app? If it is when you try to code sign your app, can you provide the command that you are using along with any logs that you may have from the console?

Also, if this command is segmentation faulting I am assuming that the Console.app has a crash report in the left column, if you could provide that it would be helpful as well.

Matt Eaton
DTS Engineering, CoreOS
meaton3@apple.com

When I try to codesign my app I am facing this issue & below is the command I am using  pkothapeta@CCILTM03 CipherCloud % codesign -s "Developer ID Application: CipherCloud Inc (ZGNQHYL3AG)" --timestamp --options runtime -f --entitlements ./Sources/CipherCloud/CipherCloud.entitlements --deep ./build/CipherCloud.app Output: ./build/CipherCloud.app: replacing existing signature zsh: segmentation fault codesign -s "Developer ID Application: CipherCloud Inc (ZGNQHYL3AG)" runtim Please find the Crash Report & entitlements files from below ref:

https://drive.google.com/file/d/14-Idpug-OZeAXxs8NvtlwOd5czIqBurB/view?usp=sharing

https://drive.google.com/file/d/18CI3cbouP4dQyESvd54BDeor8yeaFVdC/view?usp=sharing

When I try to codesign my app I am facing this issue & below is the command I am using 

pkothapeta@CCILTM03 CipherCloud % codesign -s "Developer ID Application: CipherCloud Inc (ZGNQHYL3AG)" --timestamp --options runtime -f --entitlements ./Sources/CipherCloud/CipherCloud.entitlements --deep ./build/CipherCloud.app

Output: ./build/CipherCloud.app: replacing existing signature

zsh: segmentation fault codesign -s "Developer ID Application: CipherCloud Inc (ZGNQHYL3AG)" runtim

Please find the Crash Report & entitlements files from below ref:

https://drive.google.com/file/d/14-Idpug-OZeAXxs8NvtlwOd5czIqBurB/view?usp=sharing

https://drive.google.com/file/d/18CI3cbouP4dQyESvd54BDeor8yeaFVdC/view?usp=sharing

Please find the Crash Report …

Thanks. Consider the backtrace of the main thread:

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib … semaphore_timedwait_trap + 10
1   libdispatch.dylib      … _dispatch_sema4_timedwait + 76
2   libdispatch.dylib      … _dispatch_semaphore_wait_slow + 58
3   com.apple.security     … SecCmsTSADefaultCallback + 1503

codesign is trying to generate a secure timestamp for your signature (frame 3). This is an async request and codesign is using the standard Dispatch semaphore malarkey to wait for the response (frames 2 through 0).

The actual work is happing over on the crashing thread:

Thread 1 Crashed:: Dispatch queue: com.apple.security.XPCTimeStampingService
0   libxpc.dylib       … xpc_get_type + 10
1   libxpc.dylib       … xpc_data_get_length + 14
2   com.apple.security … __sendTSARequestWithXPC_block_invoke.23 + 421
3   libxpc.dylib       … _xpc_connection_reply_callout + 36

codesign is using XPC to talk to a system service to get that timestamp. It’s got an unexpected response from that system service and then crashed trying to parse that response.

Now, codesign shouldn’t crash in this situation, and we have a bug on file about that (r. 40837360). That should be fixed in the macOS 12 beta that we’re currently seeding.

The next question is why is the timestamp service returning that unexpected response, and that’s hard to say. The timestamp service has to talk to an Apple server to get this secure timestamp. In some cases that server is temporarily broken, and we see problems like this. In other cases I’ve seen folks run into problems like this when their network environment blocks access to that server.

So, questions:

• How reproducible is this? Has it ever worked in your current environment?

• If you retry this in a different network environment — if you’re at work, try it at home, or the reverse — does it still crash?

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

Earlier this was working in my current environment(Home) & all of the sudden when I do codesign this was getting crash in my system.

This works in other environments

The fact that codesign crashes when something prevents it from accessing the timestamp service is a bug (r. 40837360).

Fixing that crash — for example, by installing macOS 12 beta — will just fix the crash. It won’t help you sign your code because the bug is being triggered by a network error accessing the timestamp service. You need to investigate why your network is blocking this network request.

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