From f0d12d93ede96d6ba032f39112cc87ce23a7e47e Mon Sep 17 00:00:00 2001 From: Ugo Mignon <56931733+TartanLeGrand@users.noreply.github.com> Date: Mon, 12 Oct 2026 12:31:10 +0200 Subject: [PATCH] Sign with a single SHA-256 CodeDirectory Zupersign always asked for a SHA-1 primary CodeDirectory with a SHA-256 alternate. codesign emits only SHA-256 for deployment targets of iOS 11 / macOS 10.13 and later, and App Store Connect rejected the pair with ITMS 90034 ('is not signed using an Apple submission certificate') even though the certificate chain, CMS signature and slots were valid. Ad-hoc signatures are unchanged. --- src/lib/Zupersign.cpp | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/lib/Zupersign.cpp b/src/lib/Zupersign.cpp index 7b941e1..b06aa27 100644 --- a/src/lib/Zupersign.cpp +++ b/src/lib/Zupersign.cpp @@ -72,7 +72,10 @@ int zsign_sign( success = asset.Init( cert, pkey, "", string(static_cast(entitlements[0].data), entitlements[0].len), - is_adhoc, false, false + // Real signatures get a single SHA-256 CodeDirectory, as codesign emits for deployment + // targets of iOS 11 / macOS 10.13 and later. App Store Connect rejects the SHA-1 primary + // plus SHA-256 alternate pair with 90034 ("not signed using an Apple submission certificate"). + is_adhoc, !is_adhoc, false ); if (!success) { *exception = strdup("Invalid developer certificate/private key");