Hello, Adding our case to the long-running thread on this issue (https://developer.apple.com/forums/thread/118465). Our team is the latest to be hit by statusCode 7000 "Team is not yet configured for notarization", and we'd like to (a) document the data points in case it helps Apple correlate cases and (b) ask the community whether anyone has seen a faster resolution path than what's been reported here over the past 6 years. Our situation Team ID: A92X4FJ5HU Last successful notarization: 2026-05-18 11:23:26 UTC First rejection: 2026-05-18 17:19:15 UTC (~6 hours later, no apparent trigger on our side) Total rejections since: 22 submissions across 9 days, 100% rejected with statusCode 7000 Open support case: 102900780153 What we have already verified Apple Developer Program membership Active (Renewal Sept 17, 2026) Apple Developer Program License Agreement: Accepted Apr 15, 2026 Free Apps Agreement: Active (Apr 15, 2026 — Sept 16, 2026) Paid Apps Agreement: Active (Mar 17, 2026 — Sept 16, 2026) Banking and tax information complete Developer ID Application certificate valid (notBefore 2025-10-12, notAfter 2027-02-01) What we tested Variable Result API key A (Admin role, created 2025-10) Rejected, statusCode 7000 API key B (Admin role, created 2026-05-22) Rejected, statusCode 7000 Same Issuer ID, both keys Same rejection Bundle ID com.matrixai.app (one product) Rejected Bundle ID com.flowith.os.beta (different product) Rejected Locally-rebuilt clean DMG Rejected Pre-existing already-signed DMG Rejected The rejection happens server-side after upload completes — authentication, signing, hardened runtime, and timestamp are all confirmed correct (codesign verifies cleanly, both keys authenticate). The submission is accepted by the notary service, then rejected with statusCode 7000 after a few minutes of "In Progress". Sample submission IDs (all rejected, statusCode 7000) ac52531f-1b9e-4210-8123-54afea90f66f (2026-05-27 10:20 UTC) baba6420-e245-4597-b229-ec5af4b309c5 (2026-05-27 10:23 UTC) 72118f71-9f1d-4ce9-8068-3eca5017104d (2026-05-27 09:49 UTC) Question to the community I've read this entire thread (all 4 pages, 6 years of reports) and the related threads (749857, 813624, 825906, 827589, 130479, 130494, 741721, 809228). The consistent answer from DTS is "this is a Developer Program Support issue, escalate via official channels", but the threads also document wait times of 1 day to 3+ months with no SLA and no transparency. A few questions: Has anyone in 2025 or 2026 had this resolved in under 2 weeks? If yes, what (if anything) on your side accelerated it? Did anyone identify a specific account-level signal (recent agreement re-acceptance, banking change, AppID/Bundle ID conflict, recent role/Account Holder change, recent device verification, etc.) that correlated with the trigger date? Is there any escalation path beyond Case → DPS → "engineers are working on it" loop? Several users on this thread report 39 days, 3 months, 4 separate cases — and DPS still cannot give an ETA. I understand the official answer is "wait for Developer Program Support". Posting this here primarily so Apple has more correlated data points for the engineering team that owns notarization, and so other developers who hit this in the future can find one more datapoint. Thanks.

Notarization has been rejecting every submission with statusCode 7000 ("Team is not yet configured for notarization") for over five weeks. I'd appreciate any Apple staff who can confirm the gate status or re-route this internally. Account: Team ID: ZLPP2G8NG3 Account type: Individual, ACTIVE membership Region: EU (Czech Republic) The submission is technically clean — this is rejected at the gate, not on content: Developer ID Application cert valid (expires 2031), full WWDR chain Signed with hardened runtime + secure timestamp codesign --verify --deep --strict passes notarytool uploads succeed, then Rejected in ~30-60s log shows "issues": null (the archive is never opened) Confirmed it is NOT app-specific: a 50 KB hello-world C binary, signed the same way, is rejected identically. Latest canary submission: 95833847-e70f-41fe-b61f-c9dc9ffd90ed (2026-05-27) -> 7000 Timeline: 2026-04-20 first 7000 rejection (app, after ~60h "In Progress") 2026-04-29 escalated to engineering (case 102873818441, advisor Ronan) 2026-05-13 advisor Ira (case 102887849530) requested government photo ID + address verification — uploaded same day via the official file-upload portal, autoreply confirmed receipt 2026-05-14 to 05-27 silence; case was closed on Apple side, issue NOT resolved 2026-05-27 still 7000 I've completed everything on my side: License Agreement accepted, Free Apps agreement Active, DSA trader designation done, and the identity-verification documents submitted on May 13. Two weeks later the gate is still down with no reply on either case. Question for Apple staff: can someone confirm whether the identity-verification documents from May 13 reached the team that flips the notarization flag, and whether anything further is needed from me? The support cases have gone quiet and I have no other channel to check status. Thank you.

Hello everyone, I enrolled in the Apple Developer Program, completed payment successfully, and received confirmation, but my developer account is still not activated after 5 business days. I’m currently unable to access developer tools or continue setup. I’ve also had difficulty getting through to Apple Developer Support directly, which has made it difficult to understand whether something is wrong with my enrollment or if this is simply an unusually long processing delay. I’ve already contacted Apple Support, but I keep getting redirected between support channels. Has anyone else experienced a similar delay recently? If so: How long did activation take for you? Was there anything specific you had to do? Did your enrollment eventually activate automatically? Any advice or shared experiences would be appreciated. Thank you.

Hi everyone, I’m having an issue with my Apple Developer Program enrollment and I’m not sure what is happening or how to proceed. I recently enrolled in the Apple Developer Program, and after submitting everything, the status showed as “In Review” for over a week. However, after that, something strange happened: The enrollment status completely disappeared from the Apple Developer app When I log into the Apple Developer website, I only see the option to “Enroll” again I can no longer find any active enrollment status anywhere I also opened support cases regarding this issue. In both cases, I received confirmation emails that the cases were created and assigned. However, I have not received any follow-up responses via email, even though I can see in the support portal that there was some kind of reply from Apple support. I double-checked my email address and there are no incoming messages from Apple Support. I also checked spam/junk folders. So at the moment I’m stuck in a situation where: My enrollment was in review It disappeared completely I cannot see any status anymore And I’m not receiving support responses via email Has anyone experienced something similar or knows what might be happening here? Any advice would be appreciated. Thanks in advance.

Hi, we're urgently trying to resolve the changing of our account membership details. We need our app developer name to match our business name as it's currently wrong. All the information can be found under the case number 102893432961. Could this please be urgently looked into?

Hi, I've seen a few posts about payment been declined, with no resolution noted on any. I have tried, Chrome and Safari, with the same response - Payment Declined. Checking my bank that payment request never reached them, so the issue lies with Apple's payment system, maybe their fraud prevention on payments. Im using my companys debit card to make the payment. How can i get this resolved? Thanks Lee

Hi everyone, Apple took $79 from my bank account last week because I wanted to sign up to sell my app on the store. In my account, it says you need to complete your purchase, but the money has been charged in my account, and I have no access to any developer account. I have sent two emails to Apple support with no reply. Does anyone know how to get a refund or how to fix this?

Hello I am trying to publish my application built through Base44 but I am struggling with one element ''Unable to Add for Review The items below are required to start the review process: You must choose a build'' I have installed XCode but I am struggling with setting the application properly. I have sent two emails to Apple Developer and been on the phone after two call back requests for nearly two hours and no response Would anyone advise how to finalise this setup and publish the app? Best wishes, Catalin

Hello, I am trying to enroll in apple developer program and I get this generic error "Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time." without any reason or clarification. I tried from my PC and from my iphone device both giving me same error. Can you check whats the problem here ? Thanks in advance!

Hello, I am trying to enroll in apple developer program and I get this generic error "Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time" without any reason or clarification , i tried from my PC and from my iphone device both giving me same error.

Hello Apple Developer Community, I’ve got a problem with the Xcode Build feature. Because when I would like to build / run my app, my iPhone won’t show up. I’ve already enabled Developer Mode and have set it up in Xcode and did the setup again. I don’t know what I can do next. Are there any possible solutions to this? Thanks for the help 😁. additional Information: Xcode Version: 26.5 Mac: MacBook Air M3 · macOS 26.5 iPhone: iPhone 16 · iOS 26.5

Hello, everyone! I've discovered a bug similar to libstdc++/115939 in GCC. This bug exists for a while. Did someone face it too? I'd be glad to accept any advise. Thank you in advance!

Hey everyone, this is a difficult topic to pin down on a certain component but I don't want to assign blame anyway. I want it to go away. Looks like people started to see this somewhere at Xcode 15 but it keeps happening. Xcode 26.5 as of this writing. For Apple people reading this, I posted a bug/feedback FB20206100 including a ready-to-compile (or rather fail-to-compile) example project. The gist is: If you open a Package.swift file with Xcode and that package contain a sub-package, Xcode will insert -suppress-warnings into the build of said sub-package. This means if you add "swiftSettings: [.unsafeFlags(["-warnings-as-errors"])]" into that sub-packages Package.swift file, it wont compile. Why? Because: error: Conflicting options '-warnings-as-errors' and '-suppress-warnings' When you look into the fairly recently accepted swift evolution propsal 0443 they basically say "That's fine. Nothing to see here." or as the proposal put it: Interaction with -suppress-warnings This proposal deliberately excludes -suppress-warnings and its group-based counterpart from the new unified model. We retain the behavior of the existing -suppress-warnings flag but forbid its usage with the new options. The following rules will be applied: It is forbidden to combine -suppress-warnings with -Wwarning or -Werror. The compiler will produce an error if these options are present in the command line together. It is allowed to be combined with -no-warnings-as-errors. The current compiler behavior permits the usage of -no-warnings-as-errors or -warnings-as-errors -no-warnings-as-errors with -suppress-warnings. We will maintain this behavior. I don't care who is right or wrong here but the bottom line is that if you use sub-packages you are effectively being errored out of using "-warnings-as-errors" for (IMHO) no good reason. Could Please someone look at this and say "Yeah, that doesn't look right, let's fix this". Please Thank You Roddi P.S.: Yes, I know there have been posts before that are lamenting this. But I thought, Let's try a fresh start here.

I am currently in the process of registering for an iOS Company Developer Account. However, when attempting to complete the Legal Authority section, I am unable to successfully enter the Registration ID and the one-time verification code; the system keeps flagging these fields with an error. I am certain that the information I am entering is correct—there are absolutely no extra spaces or typos. Please help me; I am completely stuck at this stage and cannot proceed with the registration!

I am currently in the process of registering for an iOS Company Developer Account. However, when attempting to complete the Legal Authority section, I am unable to successfully enter the Registration ID and the one-time verification code; the system keeps flagging these fields with an error. I am certain that the information I am entering is correct—there are absolutely no extra spaces or typos. Please help me; I am completely stuck at this stage and cannot proceed with the registration!

i've been trying to enroll in apple developer program since months and everytime i get this generic error "Your enrollment in the Apple Developer Program could not be completed at this time." without any reason or clarification , i tried from my own macbook pro device and from my iphone device both giving me same error without any luck , thats weird that im trying to register and never had any violation with apple and get this experience

Hello, I am unable to complete my Apple Developer Program enrollment. The enrollment fails with the generic message: “Your enrollment in the Apple Developer Program could not be completed at this time.” I contacted Apple Developer Support, followed the requested steps, completed a callback, and uploaded the requested government-issued ID and official address certificate through Apple’s secure upload link on Friday, May 22, 2026. I was told that the case would be escalated to the operations / enrollment review team, but I have not received confirmation that the documents were received or that the manual review is in progress. I have also tried the callback option again, but I have not been able to reach support successfully. Could Apple Developer Support please advise on the correct escalation path for an enrollment case that remains blocked after the requested documents have already been submitted? I can provide the case number privately through an official Apple Support channel if needed. Thank you.

Hi, I have the NFC &SE entitlement but still not able to read a pass from the apple wallet on another iphone. The logs show that the NFCVASReader session is initialised and the readerSessionDidBecomeActive — session is live, waiting for pass tap, but nothing is read. The pass is nfc enabled with correct encryption key. It feels like I am still missing some kind of entitlement to read VAS from passes - could anyone advise please?

Hullo, I wanted to turn a class in a struct and move intelligence in a protocol extension, but when I try to call inits in the extension I get 'self' used before 'self.init' call or assignment to 'self' How do I call self.init or assign to self before updating the values? Of course init does no accept mutating.

Xcode 26.5 downloads darwin-arm64 Claude Agent binary on Intel Macs, causing exec failure misreported as code-signing error (workaround verified) On Intel Macs, Xcode 26.5 (build 17F42) downloads the darwin-arm64 build of the Claude Agent rather than the darwin-x64 build that the vendor publishes at the same version. The arm64 binary fails to exec on Intel with NSPOSIXErrorDomain Code=86 ("Bad CPU type in executable") and Xcode's Intelligence subsystem then surfaces this in the UI as a code-signing / sandboxing failure. Replacing the downloaded binary with the parallel darwin-x64 build, and updating the agent's Info.plist checksum and URL to match, results in a fully functional Claude Agent in Xcode 26.5 on the same Intel Mac. This was verified end to end on the affected hardware. The agent downloader in Xcode should select the URL matching the host CPU architecture (e.g. by inspecting the result of uname -m or the equivalent in Foundation). This appears to be an isolated fix to whichever component constructs the agent's download URL in Xcode's Intelligence subsystem. Secondary suggestion: the user-facing error message "the code signing identity for the agent did not match expectations, or the agent violated sandboxing rules" should be revised when the underlying cause is an exec failure (EBADARCH or otherwise). The current wording is misleading and has produced considerable misdirected investigation in the developer community. USER-SIDE WORKAROUND (VERIFIED) The following restores Claude Agent functionality on this Intel Mac running Xcode 26.5. It may need re-applying after Xcode updates the agent, since the buggy download logic will run again. Quit Xcode. Download the parallel darwin-x64 binary from the vendor's release bucket (the same URL as in the Info.plist, with "darwin-arm64" replaced by "darwin-x64"). Make the destination writable, copy in the new binary, restore read-only mode. Recompute SHA-512 and update Info.plist's checksum and url fields with plutil. Relaunch Xcode. Workaround for Intel Mac users (verified) This restores a working Claude Agent in Xcode 26.5 on Intel until Xcode'sdownloader is fixed. Quit Xcode fully first. 1. Quit Xcode osascript -e 'tell application "Xcode" to quit' sleep 3 2. Download the correct-arch binary directly from Anthropic's release bucket curl -fL -o /tmp/claude-x64\ttps://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.118/darwin-x64/claude chmod +x /tmp/claude-x64 3. Verify it's the right arch and properly signed file /tmp/claude-x64 # → Mach-O 64-bit executable x86_64 codesign --verify --verbose /tmp/claude-x64 4. Replace the arm64 binary Xcode downloaded (destination is read-only by default) AGENT_DIR=~/Library/Developer/Xcode/CodingAssistant/Agents/XcodeVersions/17F42/claude chmod u+w "$AGENT_DIR/claude" cp -p /tmp/claude-x64 "$AGENT_DIR/claude" chmod a-w "$AGENT_DIR/claude" 5. Update Info.plist so its checksum and URL match the swapped binary NEW_CHECKSUM=$(shasum -a 512 "$AGENT_DIR/claude" | awk '{print $1}') plutil -replace checksum -string "$NEW_CHECKSUM" "$AGENT_DIR/Info.plist" plutil -replace url -string "https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.118/darwin-x64/claude" "$AGENT_DIR/Info.plist" 6. Relaunch Xcode; the Claude Agent now works on Intel. Caveats Adjust 17F42 and 2.1.118 to whatever your Xcode build and agent version actually are. Check with ls ~/Library/Developer/Xcode/CodingAssistant/Agents/XcodeVersions/ and the version key in the Info.plist. The workaround may not survive an Xcode update. If Xcode refreshes the agent (new Claude Code version, new Xcode point release), the buggy download logic will run again and overwrite the x86_64 binary. The same procedure restores working state. Worth saving the commands above as a small shell script so you don't have to re-derive them next time. ENVIRONMENT Hardware: MacBook Pro 2019, Intel Core i9 (x86_64) macOS: 26.5 Xcode: 26.5 (build 17F42) Agent: Claude Code 2.1.118 Account: Claude Pro (claude.ai OAuth) I have tried unsuccessfully to request via 'Apple Feedback Assistant' that the above problem be looked into. This was their response: "Thank you for your feedback, it is noted. Engineering has determined that there are currently no plans to address this issue. This feature relies on the dedicated Neural Engine found on Macs with Apple silicon (M1 or newer) to provide the necessary performance and capabilities. As a result, systems that do not include this hardware are not supported for this specific workflow. You can close this feedback by selecting "Close Feedback" via the Actions button found above. This Feedback will no longer be monitored, and incoming messages will not be reviewed. " Clearly no one from the senior engineering team has looked at this or given it any consideration and they are not interested in making a trivial fix within Xcode so that it selects the correct Claude binary for download. It is frustrating that Apple's response cites the requirement for a 'neural engine found in M-series Macs' , when this is very clear to any developer that Claude does not make use of this feature and it self-evidently works on x86 hardware without it . If anyone has any ideas how to get a response from a helpful senior Xcode developer, I would be most interested. I can understand Apple are reluctant to put any effort into old hardware, however they still provide an up to date Xcode for the x86 platform and I don't think it is asking too much to fix a simple bug which would make life easier.