Apple M1 Pro, 26.5.1 (25F80) XCode 27.0 Beta (27A5194q) Command Line tools for Xcode 27 are installed. Device Hub Version 27.0 (235.4.2) Within device hub I can not create iOS 27 simulators. Only the 26.5 simulators are listed there. I installed the iOS 27.0 SDK. Also deleted and reinstalled it. The computer was restarted. No change. I am unable to create the proper iOS 27 Simulators. Any idea why this is not working? Thanks for the help upfront.

On iOS 26, a Simulator screen recording shows the bottom corners of content go from rounded to square during normal push and sheet transitions. This happens on the simulator, but I don't see this on a real iPhone. Steps to reproduce: Create a new SwiftUI app and use the attached content view. Run on an iOS 26 Simulator. Start a Simulator screen recording. Tap a row to push, and tap "Filter" to present the sheet. Stop the recording and play it back frame by frame. Run the same app on a real iPhone and watch the transitions live. Question: Is this a new feature or a simulator bug? Configuration: Xcode 26.4.1 iOS 26 Simulator — iPhone 17 Pro Real device: iPhone 16 Pro Max Attachments: ContentView

Nothing changed on my end, Pro subscription still active, but Xcode 26.5 (17F42) simply does not want to log into Codex anymore. It opens the OAuth flow and after finishing and closing the window, it still says "Not Signed In". Codex login works everywhere else, including the Codex app. What to do?

On https://developer.apple.com/documentation/AppIntentsTesting/testing-your-app-intents-code Apple showcases the following example using AppIntentsTesting to query entities indexed in spotlight. For me, calling .spotlightQuery on any entity definition causes a crash. func testAllEventsIndexed() async throws { let eventDef = definitions.entities["EventEntity"] let allIndexed = try await eventDef .spotlightQuery(nil) XCTAssertGreaterThanOrEqual(allIndexed.count, 3) } Crash: expression unexpectedly raised an error: Failed to obtain the result of the distributed invocation after it was executed. Remote threw executionPermissionDenied(requestBundleID: Is anyone else seeing this crash, or is it just me? Thanks!

Filed a feature request in feedback assistant, but starting a discussion here as well since I'm probably not the only one. The issue I have is that coding assistant and previews seem to be mutually exclusive. That means that when I'm iterating on UI, I either have to rely on the coding assistant showing me preview screenshots (cannot interact), firing up Device Hub (have to manually kick off a build after each change) or manually opening the associated preview (requires a lot of hoping back and forth). This feels inefficient and means I have to hop around and manage my windows and tabs more. A slight work around is to open a split view with the file and preview there. This layout is inefficient and clunky. I would love if Xcode supported a pinned preview next to coding assistant (or automatically showed the relevant one). I imagine this working just like showing a preview next to a file cmd + opt + return hides/shows the preview. FB23219611

Anyone else seeing a lot more "Class X is implemented in both ..." warnings on Xcode 27 than on Xcode 26? Same source, same flags, the count goes from a handful to a couple thousand, and some now correlate with real crashes (cast failures, missing protocol conformances) instead of the usual harmless first-wins behavior. Is this a known change in Swift 6.4 / Xcode 27? Is there a new flag I should be passing? Any suggestions welcome.

It doesn't seem to be able to launch. It says "This version of Xcode is not compatible with this version of macOS." So, does that mean that users who have updated to macOS 27 cannot submit apps to the App Store? Do I have to wait until Xcode 27 starts accepting submissions? Environment: macOS 27.0 / Xcode 26.6 RC

With the latest Xcode 26.4 my project fails to compile due to a "compiler unable to type-check in reasonable time" error with a library I've been using for years and has not changed. The library is https://github.com/ngageoint/mgrs-ios and is specifically around this line https://github.com/ngageoint/mgrs-ios/blob/master/mgrs-ios/utm/UTM.swift#L96. Since this isn't my library I can't change it, but again we've been using this library for years now without issue - it was only when Xcode updated this morning that our compilation workflow broke. (Compilation machine is an M3 Pro with 18GB of RAM, so I don't think that's the problem here)

Hi, I saw the mac os 27 new features video https://developer.apple.com/videos/play/wwdc2026/224/?time=64 and was trying Provisioning and i get this warning [Internal] Thread running at User-interactive quality-of-service class waiting on a lower QoS thread running at Default quality-of-service class. Investigate ways to avoid priority inversions at the line try startupOptions.setGuestProvisioning(opts) i have my vm q declared like this let vmQueue = DispatchQueue(label: "VZVirtualMachineQueue", qos: .userInteractive) and i am executing like this self.vmQueue.async { [weak self] in ......... ......... let startupOptions = VZMacOSVirtualMachineStartOptions() try? startupOptions.setGuestProvisioning(opts) vm.start(startupOptions) } and it fails with treading warning and provisioning does not happen. Thanks in advance for the help

Hey all, the codex sign in isn't working for me in Agents. I am using the 26.5 release candidate version. It always says "Not Signed In". I have completed the Sign In process multiple times. Anyone else seeing this? I have filed Feedback FB22732574

My switch from an individual to an organization enrollment (ID: 484G9X5T3Z) has been pending for more than seven weeks, and recent follow-up requests to Apple Developer Program Support for status (case numbers: 102880166579 and 20000117404816) have gone unanswered. In the meantime, I have paid for the renewal of my subscription but since member benefits are suspended during migration I haven't been able to use it for more than a month. Please Apple, let me know if there is anything I need to do to get my enrollment switch completed.

Hello, I am posting here as a last resort because I have been unable to get any assistance through Apple Developer Support. Case ID: 102888399005 Timeline: I started the Apple Developer Program enrollment process using the Apple Developer app on my iPhone. I successfully uploaded my ID document. After that, I received a message stating that my identity could not be verified. I submitted a support request to Apple Developer Support. I received a reply from Developer Support, but the response did not address my issue or provide any guidance on how to continue the enrollment process. The status in the Apple Developer app on my iPhone later changed to "ID Verification Rejected". I replied to the existing support case and, after receiving no response for two weeks, submitted a new support request. Several weeks have now passed without any response to either request. The enrollment page on the web now displays the message: "Your enrollment could not be completed." The Apple Developer app for iOS still shows "ID Verification Rejected" In the Apple Developer app for macOS, I am able to start the enrollment process. However, after scanning my ID document, the app either displays a completely black image or crashes immediately. At this point, I have multiple open support requests and an unresolved case, but I have not received any guidance on why my identity verification was rejected or how I can proceed with enrollment. I would greatly appreciate any assistance, guidance, or help in getting this case reviewed by the appropriate team. Thank you for your time. Best regards, Jan Bula

I submitted this to Feedback Assistant as FB22331090 and wanted to share a minimal reproducible example here in case others are seeing the same issue. Environment: Xcode 26.4 or Xcode 26.3 Apple Swift version 6.3 (swiftlang-6.3.0.123.5 clang-2100.0.123.102) Effective Swift language version 5.10 Deployment target: iOS 17.0 The sample app builds successfully for normal development use, but archive fails. The crash happens during optimization in EarlyPerfInliner while compiling the synthesized deinit of a nested generic Coordinator class. The coordinator stores a UIHostingController. Minimal reproducer: import SwiftUI struct ReproView<Content: View>: UIViewRepresentable { let content: Content func makeUIView(context: Context) -> UIView { context.coordinator.host.view } func updateUIView(_ uiView: UIView, context: Context) { context.coordinator.host.rootView = content } func makeCoordinator() -> Coordinator { Coordinator(content: content) } final class Coordinator { let host: UIHostingController<Content> init(content: Content) { host = UIHostingController(rootView: content) } } } Used from ContentView like this: ReproView(content: Text("Hello")) Steps: Create a new SwiftUI iOS app. Set deployment target to iOS 17.0. Add the code above. Archive. Expected result: Archive succeeds, or the compiler emits a normal diagnostic. Actual result: The Swift compiler crashes and prints: "Please submit a bug report" "While running pass ... SILFunctionTransform 'EarlyPerfInliner'" The crash occurs while compiling the synthesized deinit for ReproView.Coordinator. Relevant log lines from my archive log: line 209: Please submit a bug report line 215: While running pass ... EarlyPerfInliner line 216: for 'deinit' at ReproView.swift:19:17 One more detail: The same sample archived successfully when the deployment target was higher. Lowering the deployment target to iOS 17.0 made the archive crash reproducible. This may be related to another forum thread about release-only compiler crashes, but the reproducer here is different: this one uses a generic UIViewRepresentable with a nested Coordinator storing UIHostingController.

Hi everyone, I’m looking for advice or shared experiences regarding the Apple Developer Program membership conversion process from an Individual membership to an Organization membership. I submitted my request more than two months ago, but the process still does not appear to have started. Current support cases: Case 102844790649 Case 102884491745 I have followed up multiple times, but several follow-up emails did not receive any response, which has made it difficult to understand the actual status of the request. I have already confirmed that: Two-factor authentication is enabled on my Apple Account My organization has a valid and publicly accessible website I am ready to proceed with the migration However, I still have not received confirmation that the migration has officially begun. I would appreciate advice from anyone who has gone through this process: Is it normal for the Individual → Organization membership conversion to take more than two months? Did you receive confirmation when the migration officially started? Were there any escalation methods that helped move the process forward? Is it safe to continue publishing apps while the migration request is pending? Any advice or shared experiences would be greatly appreciated. Thank you.

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.

Our account has been disabled/removed from enrolment in the Apple developer program, without any explanation. When we reached out to Apple about this, they asked for documentation (which they already have been provided in the past, and accepted without issue) such as our company documentation and personal identification. It’s been well over two weeks now, and we have not heard back from Apple. When we reach out to developer support they advise there is nothing they can do and we are waiting on some “internal“ team. As a result, our push notifications on live apps have stopped working (due to certificates being revoked), as well as many other issues. Would someone from Apple please advise how to escalate this, so that some action can be taken?

PROVIDE TRACKS OF THE CREATION OF ILLEGAL PERSONALIZATION PRIVACY AND DEVPOLOVER PLATFROM BUSINESS COMMUNITY WHERE IT WAS CREATED AND WHEN IT WAS CREATED. PROVIDE A VERY ACCURATE DATE, TIME, DEVICE, LOCATION AND DO NOT LOSE THE TRACKS OF THE PERPETRATOR WHO IS CLAIMING TO BE THE OWNER OF THE RIGHTS OF THE ACCOUNT OWNER OF MY DATA THAT WAS OBTAINED, THANK YOU.

Earlier from the apple documentation, there was an option to get the API difference between OS. That option is no longer present. How do we get the API difference now. Is there anyway we can get this.

Hello, I am unable to notarize any macOS app/archive with my Apple Developer Team. Every submission is rejected with the same account/team-level error: statusCode: 7000 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. The notarization log has: issues: null ticketContents: null This does not look like a code signing or binary validation issue, because multiple different archives/apps fail with the same statusCode 7000. My recent submission history: 2026-05-22 06:25 MSK, ClipDose.dmg, b967a63b-ce9f-486d-805f-a6853ceaf447, Rejected 2026-05-22 07:02 MSK, ClipDose.dmg, 0dd03db8-267d-4b15-bde7-21bd8f22adec, Rejected 2026-05-22 07:39 MSK, ClipDose.dmg, e79f831f-22e9-47b8-9578-344a5067e34c, Rejected 2026-05-22 14:09 MSK, ClipDose.dmg, 01f1bdb3-3323-4952-b735-0e984cad8737, Rejected 2026-05-22 16:58 MSK, ClipDose.dmg, 3e82d154-517f-4e3c-8808-4f6504c05f35, Rejected 2026-05-22 23:30 MSK, FLEX_VIDEO-notary.zip, 7cbc3fa1-749d-4fa3-bab7-18644019d81b, Rejected 2026-05-23 08:41 MSK, FLEX_VIDEO-0.9.2-macOS.dmg, edf241b0-7a0b-4c26-98a8-d3c6f869b0e1, Rejected 2026-05-23 08:47 MSK, SmokeNotary.dmg, 39c9fdf5-0baa-453c-bdd1-7b884fd9e96a, Rejected 2026-05-30 19:58 MSK, SmokeNotary.dmg, 8e14b3a1-5721-4e1a-ab43-000852630e29, was In Progress for about 9 days 23 hours before finally becoming Rejected 2026-05-30 20:43 MSK, FLEX_VIDEO-notary.zip, 1700b9b2-17b5-47c9-8854-cbdbc342d708, Rejected 2026-06-01 18:36 MSK, FLEX_VIDEO-notary.zip, 3d4c986d-af30-4c5c-a987-05ed09b16189, Rejected I have already contacted Apple Developer Programs Support by email / support contact as requested by the notarytool log, but I have not received any response. Could someone from Apple please confirm what exactly needs to be enabled or fixed for this Developer Team? Is statusCode 7000 something that only Apple can resolve on the backend? Thank you.

Hello Apple Developer Support, I am requesting maximum escalation for this case. My paid Apple Developer Program account has been unusable for Developer ID notarization for more than two weeks. This blocks macOS distribution entirely, despite the fact that the membership is active and all visible account requirements appear to be completed. Team ID: GRP4HM9M63 Apple Developer Program: Active Account status already checked: Apple Developer Program membership is active Apple Developer Program License Agreement is accepted Apple Developer Agreement is accepted Free Apps Agreement is active W-8BEN tax form is active Developer ID Application certificate exists and is active The applications are signed with Developer ID Application Hardened Runtime is enabled Local codesign verification passes Despite this, notarization is still unavailable for this Team. This is not an issue with a specific app, archive, DMG, ZIP, signing configuration, or binary validation. Multiple different apps and archives are rejected with the same account-level error before binary validation. Recent failed submissions: Cassini.zip Submission ID: a429460d-cdf9-47cc-9731-90bac71286af Status: Rejected Status code: 7000 Status summary: “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.” Issues: null Lunoura.zip Submission ID: 3aa46853-b3c7-4076-a08d-f9e4db9bea64 Status: Rejected Status code: 7000 Status summary: “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.” Issues: null Earlier submissions for Cassini.dmg and Cassini.zip were also rejected with the same statusCode 7000. Since multiple unrelated archives are affected and all logs contain issues: null, this clearly appears to be a Developer Team/account configuration issue on Apple’s side, not an application validation issue. Please escalate this case to the appropriate Developer Program / notarization backend team and urgently check the notarization configuration for Team ID GRP4HM9M63. Please explicitly confirm: Whether Team ID GRP4HM9M63 is currently enabled for Developer ID notarization. Whether there is any hidden account, KYC, legal, compliance, tax, or backend configuration issue blocking notarization. Whether Paid Applications Agreement or bank account setup is required for Developer ID notarization, even though we are not distributing paid apps. What exact action is required from our side. When this paid Developer Program account will become usable for Developer ID notarization. This issue has already blocked us for more than two weeks. We are paying for Apple Developer Program membership, but cannot use a critical Developer ID distribution feature.