Post

Replies

Boosts

Views

Activity

Update: reproduced with a brand-new Bundle ID — this is account/Team-side, not project-side
To rule out anything stuck on the original App ID, I created a completely new Bundle ID (br.com.minhapecuaria.ios2) from scratch: New App ID registered in the portal, Sign In with Apple capability enabled. New App Store provisioning profile generated and installed, tied to that Bundle ID. New app record created in App Store Connect for it. Manual signing in Xcode, explicitly selecting the new Distribution certificate + new profile. Verified via codesign/security cms -D: Apple Distribution identity, get-task-allow: false, no device list — a genuine App Store signature. Uploaded via Xcode Organizer → same result: error 90034 ("Missing or invalid signature... not signed using an Apple submission certificate"). Since this Bundle ID never existed before, there was nothing "stuck" on it — no stale provisioning history, no cached signing decision tied to that specific App ID. The fact that the error persists identically rules out anything project-specific and points squarely at the account/Team level (Team ID 395DDXTXHC). I've also opened a support case (20000125779862) with this exact evidence, but so far only received generic first-line responses (certificate basics, Feedback Assistant suggestions) that don't address the account-level nature of the issue. Posting here in case anyone has seen this specific pattern — same 90034 across two independent Bundle IDs/certs/profiles under the same Team.
1
0
299
Aug ’26
Error 90034 on every App Store upload, including a brand new Xcode project
Hello, I’m experiencing a persistent App Store Connect upload issue that seems unrelated to my project. Every upload is rejected with: Validation failed (409) Missing or invalid signature. The bundle is not signed using an Apple submission certificate. (Error 90034) What I have already verified: Apple Developer membership is active. I am the Account Holder. Apple Distribution certificate exists and is valid. App Store provisioning profile was recreated. Automatic signing is enabled. Archive is exported using “App Store Connect” distribution. The exported IPA is signed with Apple Distribution (verified with codesign). I tested both Xcode Organizer and Transporter. I created a brand new native Xcode “Hello World” project, and it fails with exactly the same error. The project contains no frameworks, no CocoaPods, no Swift Packages, no Flutter, no React Native, and no embedded binaries. Since even a brand new Xcode project fails, I believe this is related to my Apple Developer account or App Store Connect validation infrastructure rather than the project itself. Has anyone experienced this before or knows what else can be verified? Team ID: 395DDXTXHC Thank you.
1
0
415
Aug ’26
App Store submission rejected with error 90034 despite Apple Distribution signature
Hi, I’m trying to submit my iOS app Minha Pecuária to App Store Connect, but Apple consistently rejects the build with: Validation failed (409) Missing or invalid signature. The bundle ‘br.com.minhapecuaria.ios’ is not signed using an Apple submission certificate. Error 90034. I have already verified that: The app is signed with an Apple Distribution certificate. The App Store provisioning profile is linked to the correct Distribution certificate and Bundle ID. Automatic signing is enabled in Xcode. The exported IPA was independently checked and shows Apple Distribution as the signing authority. The same error occurs through both Xcode Organizer and Transporter. I also reproduced the problem with a clean/new project. Could anyone from Apple or anyone who has experienced error 90034 confirm what could cause Apple’s server to reject a binary that is correctly signed with Apple Distribution? Thanks!
5
0
1.2k
Aug ’26
Update: reproduced with a brand-new Bundle ID — this is account/Team-side, not project-side
To rule out anything stuck on the original App ID, I created a completely new Bundle ID (br.com.minhapecuaria.ios2) from scratch: New App ID registered in the portal, Sign In with Apple capability enabled. New App Store provisioning profile generated and installed, tied to that Bundle ID. New app record created in App Store Connect for it. Manual signing in Xcode, explicitly selecting the new Distribution certificate + new profile. Verified via codesign/security cms -D: Apple Distribution identity, get-task-allow: false, no device list — a genuine App Store signature. Uploaded via Xcode Organizer → same result: error 90034 ("Missing or invalid signature... not signed using an Apple submission certificate"). Since this Bundle ID never existed before, there was nothing "stuck" on it — no stale provisioning history, no cached signing decision tied to that specific App ID. The fact that the error persists identically rules out anything project-specific and points squarely at the account/Team level (Team ID 395DDXTXHC). I've also opened a support case (20000125779862) with this exact evidence, but so far only received generic first-line responses (certificate basics, Feedback Assistant suggestions) that don't address the account-level nature of the issue. Posting here in case anyone has seen this specific pattern — same 90034 across two independent Bundle IDs/certs/profiles under the same Team.
Replies
1
Boosts
0
Views
299
Activity
Aug ’26
Error 90034 on every App Store upload, including a brand new Xcode project
Hello, I’m experiencing a persistent App Store Connect upload issue that seems unrelated to my project. Every upload is rejected with: Validation failed (409) Missing or invalid signature. The bundle is not signed using an Apple submission certificate. (Error 90034) What I have already verified: Apple Developer membership is active. I am the Account Holder. Apple Distribution certificate exists and is valid. App Store provisioning profile was recreated. Automatic signing is enabled. Archive is exported using “App Store Connect” distribution. The exported IPA is signed with Apple Distribution (verified with codesign). I tested both Xcode Organizer and Transporter. I created a brand new native Xcode “Hello World” project, and it fails with exactly the same error. The project contains no frameworks, no CocoaPods, no Swift Packages, no Flutter, no React Native, and no embedded binaries. Since even a brand new Xcode project fails, I believe this is related to my Apple Developer account or App Store Connect validation infrastructure rather than the project itself. Has anyone experienced this before or knows what else can be verified? Team ID: 395DDXTXHC Thank you.
Replies
1
Boosts
0
Views
415
Activity
Aug ’26
App Store submission rejected with error 90034 despite Apple Distribution signature
Hi, I’m trying to submit my iOS app Minha Pecuária to App Store Connect, but Apple consistently rejects the build with: Validation failed (409) Missing or invalid signature. The bundle ‘br.com.minhapecuaria.ios’ is not signed using an Apple submission certificate. Error 90034. I have already verified that: The app is signed with an Apple Distribution certificate. The App Store provisioning profile is linked to the correct Distribution certificate and Bundle ID. Automatic signing is enabled in Xcode. The exported IPA was independently checked and shows Apple Distribution as the signing authority. The same error occurs through both Xcode Organizer and Transporter. I also reproduced the problem with a clean/new project. Could anyone from Apple or anyone who has experienced error 90034 confirm what could cause Apple’s server to reject a binary that is correctly signed with Apple Distribution? Thanks!
Replies
5
Boosts
0
Views
1.2k
Activity
Aug ’26