Michael Eisel

@mattmassicotte would you by any chance have a combo JSON file + the dSYM it was for so I can try symbolicating myself? E.g., you posted this [JSON](https://github.com/ChimeHQ/Meter/blob/main/MeterTests/Resources/real_report.json) before, so...

Yeah, any ideas what the issue is with this code? Shouldn't it trigger the diagnostic payload to be delivered? Neither `-didReceiveMetricPayloads:` nor `-didReceiveDiagnosticPayloads` are ever called unless I trigger a...

Cool, got it now. If we look at the stack frame starting at line 23 in the JSON, we see an `address` of 4308000108 and `offsetIntoBinaryTextSegment` of 4307976192. If we...

Hang on a sec... for *crash diagnostics*, it seems that's the case. But for the one CPU exception diagnostic report I'm looking at, the offsets are much smaller, like you...

Yeah, CPU exceptions, at least when I tested them when making this issue, don't add the load address in.

IIRC symbolication is possible by giving it a load address of 0

About one second

Perhaps we could go with the more conservative approach, of adding `--digest-algorithm=sha1` instead. This will keep code signing, but it will use sha-1, which is faster than the default sha-256....

Well, in my testing using sha-1 reduces signing time from 3 minutes to 2.5 minutes. So, not a huge win.

I see, well put in a big +1 for me. It would make editing files with a shiftwidth of 2, etc. much easier.