Dashboard › spotlight › Distillation
162cf52a-f03e-4e2b-822d-21a444c860b6["78384c5d85b9c423b63fd52aa699ec25","aaa5a12e4e91f08a202b99e98f18b5be","5b1691aaed0b53ecf3f268c638881eab","918ff6c31621e49c55a6058dadebbda5","0547c840734cb058e12d3ccb256cd26f","92351694da4b1484e9b04492644f024a","fb1096ba5129c131a2690ee476fe01bb","444891085c20beb4dbed4e3f3c468bb6","f3b3b21d435a6b2dd0227b083cc39ce9","9dc0b4b553798253477e42ed4500f594"]
jq .private_key -r, replicating pipeline): single line, 201 bytes, no literal escaped \n, openssl PEM parse FAILED ("Could not read key from /tmp/opencode/k.pem") — the value is the raw base64 DER body of a PKCS#8 EC key with no -----BEGIN PRIVATE KEY-----/-----END PRIVATE KEY----- header/footer and no line wrapping (actual base64 content omitted from record — sensitive key material).cat /tmp/apple_key.json | jq .private_key -r > /tmp/apple_key.pem writes the bare base64 DER blob with no PEM armor. Xcode 16's notarytool tolerated this; Xcode 26's notarytool rejects it, producing "Error: inv..." (invalid key), which crashes electron-builder's old JSON-parsing error handler. This is the actual fix needed — not the previously discussed electron-builder 26.15.7 upgrade, which the assistant noted "only changes the error message, not the outcome."