Device Details: MBP M2 Pro AND MBP M3 Pro macOS 26.3 (25D125) Xcode Version 26.3, 26.2, 26.1 (I reinstalled all 3 of these after the macOS update) BUG: Xcode hangs indefinitely when performing Source Control operations (Pull or Push) on a Git repository that uses SSH authentication. The same repository works correctly when performing the equivalent Git operations from the Terminal using the Git CLI. The issue appears to be specific to Xcode’s internal Source Control integration. When the operation is triggered from Xcode, the UI shows a spinning progress indicator and never completes. Terminal Git commands (git fetch, git pull, git push) complete normally using the same SSH key and repository. A hang sample taken during the issue shows the Xcode main thread blocked in Source Control authentication and fingerprint handling code paths, including: IDESourceControlUIHandler IDESourceControlFingerprintManager handleAuthenticationFailure showFingerprintAlertOnWindow This suggests Xcode may be waiting on a Source Control authentication or host fingerprint UI flow that never resolves. SSH connectivity itself is functioning correctly: ssh -T git@bitbucket.org and ssh -T git@github.com both authenticate successfully. git ls-remote, git fetch, git pull, and git push all work correctly from Terminal. No Source Control accounts are configured in Xcode Preferences. Authentication relies entirely on SSH keys. Steps to Reproduce Configure an SSH key for Git access (e.g., Bitbucket or GitHub) and confirm it works via Terminal. Clone or open an existing Git repository that uses SSH (git@host:repo.git). Open the project/workspace in Xcode. In Xcode, attempt a Source Control operation such as: Source Control → Pull Source Control → Push Observe that Xcode displays a spinning progress indicator and does not complete the operation. Logs available on this Feedback Assist ID: FB22146913

I’m seeing a regression in Xcode 26.4 where Interface Builder will not allow connecting IBOutlets or IBActions. Symptoms: The usual gutter circle/dot does not appear next to IBOutlet / IBAction in the code editor Because of this, I cannot: drag from storyboard → code drag from code → storyboard The class is valid and already connected to the storyboard (existing outlets work) Assistant Editor opens the correct view controller file Important: The exact same project, unchanged, works perfectly in Xcode 26.3. I can create and connect outlets/actions normally there. ⸻ Environment Xcode: 26.4 macOS: 26.4 Mac Mini M4 Pro 64G Ram Project: Objective-C UIKit app using Storyboards This is a long-running, ObjC, project (not newly created) ⸻ What I’ve already tried To rule out the usual suspects: Verified View Controller Custom Class is correctly set in Identity Inspector Verified files are in the correct Target Membership Verified outlets are declared correctly in the .h file: @property (weak, nonatomic) IBOutlet UILabel *exampleLabel; Opened correct file manually (not relying on Automatic Assistant) Tried both: storyboard → code drag code → storyboard drag Tried using Connections Inspector Clean Build Folder Deleted entire DerivedData Restarted Xcode Updated macOS to 26.4 Ran: sudo xcodebuild -runFirstLaunch Confirmed required platform components installed Reopened project fresh ⸻ Observations In Xcode 26.4 the outlet “connection circles” are completely missing In Xcode 26.3 they appear immediately for the same code Existing connections still function at runtime — this is purely an Interface Builder issue ⸻ Question The gutter circles appearance has always been flaky in Xcode over the 13+ years I've been using it but now with 26.4 they have completely disappeared. Has anyone else seen this in Xcode 26.4, or found a workaround? At this point it looks like a regression in Interface Builder, but I haven’t found any mention of it yet.

Been working for several days trying to figure out a solution. I'm building a plugin to bring in OpenRouter into Xcode so you can choose pretty much whatever cloud LLM you want easily. One thing I'm having trouble with is artifacts in the right hand pane. Specifically in /plan mode. Currently, it will write the plan in the transcript, it will even create a markdown card, but it will not put it in the artifact pane for preview and inline comment annotation for the next prompt. I can't seem to find the answer. Any help would be appreciated.

I am posting here following the DTS Engineer’s recommended reply for cases that have already been opened with Apple Developer Program Support. Since May 2026, every notarization submission made by my active Apple Developer Program team has failed with the same account-level error: Status code: 7000 Status summary: Team is not yet configured for notarization This has continued across three calendar months and affects every file tested, including a minimal smoke-test DMG. The notarization logs contain no software-specific findings: issues: null ticketContents: null I have already followed all instructions provided by Apple Support: Submitted a valid government-issued identity document. Submitted proof of address. Provided English translations of the requested documents. Confirmed that the Apple Developer Program membership is active. Accepted the latest Apple Developer Program License Agreement. Confirmed that a valid Developer ID Application certificate is installed. Repeated the test with newly created and newly signed files. The result remains unchanged. The latest smoke-test submission was also immediately rejected with status 7000: Submission ID: e6ca0aa3-2c32-4b90-b12f-04f2dad5b46b Submission date: July 17, 2026 I understand from the DTS Engineer’s recommended reply that this issue must be handled through official Apple Developer Program Support channels and cannot be resolved by DTS on the forums. I have followed that route repeatedly, but the team is still not enabled for notarization and I have not received an effective resolution. Could an Apple representative please confirm that these cases have been escalated to the internal team responsible for Developer ID notarization provisioning? This does not appear to be a code-signing, packaging, or local Xcode issue because even a minimal test image fails with the same account-level status before any software issues are reported. I am ready to provide any additional verification requested through the existing support case. I need a specific status update and confirmation that the notarization entitlement for my team is being investigated.

My builds failed today with this error: Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases. The thing is, I have Xcode Cloud configured to use the latest release. There is a separate configuration for "Latest beta or release", so why is it using the Xcode 16.2 Beta 3 build? This is clearly a beta. If you're going to give me an option to use the latest release, then it should do what it says.

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)).

Dear The IT Crowd Cafferata, The D-U-N-S Number for The IT Crowd is 491032646. If you have the legal authority to bind your company to Apple Developer Program agreements, you can use this number to enroll for your company. Before enrolling, please ensure that The IT Crowd is a legal entity. Enroll now Best regards, Apple Developer Relations than it is stopped with this Error:This organization could not be verified as a legal entity. If you are a sole proprietorship/single person company, enroll as an individual. If this organization should be listed as a legal entity, update your D&B profile. I cheked to multiple times at DUN so the info is ok! I copy all the info direct from the mail and type it. When i use the page i see: Failed to load resource: the server responded with a status of 401 (Unauthorized) npm.angular.bundle.js?v=4768:14 Possibly unhandled rejection: undefined (anonymous) @ npm.angular.bundle.js?v=4768:14 push.1055.$get @ npm.angular.bundle.js?v=4768:9 l @ npm.angular.bundle.js?v=4768:17 $digest @ npm.angular.bundle.js?v=4768:17 $apply @ npm.angular.bundle.js?v=4768:18 H @ npm.angular.bundle.js?v=4768:10 g @ npm.angular.bundle.js?v=4768:10 (anonymous) @ npm.angular.bundle.js?v=4768:10 XMLHttpRequest.send (anonymous) @ npm.angular.bundle.js?v=4768:10 T @ npm.angular.bundle.js?v=4768:10 _ @ npm.angular.bundle.js?v=4768:10 f @ npm.angular.bundle.js?v=4768:17 (anonymous) @ npm.angular.bundle.js?v=4768:17 $digest @ npm.angular.bundle.js?v=4768:17 $apply @ npm.angular.bundle.js?v=4768:18 (anonymous) @ npm.angular.bundle.js?v=4768:18 s @ npm.angular.bundle.js?v=4768:18 (anonymous) @ npm.angular.bundle.js?v=4768:8 setTimeout (anonymous) @ npm.angular.bundle.js?v=4768:8 s @ npm.angular.bundle.js?v=4768:18 onDidSubmitForm @ app.bundle.js?v=4768:1181 fn @ VM101:4 $ @ npm.angular.bundle.js?v=4768:18 $eval @ npm.angular.bundle.js?v=4768:18 $apply @ npm.angular.bundle.js?v=4768:18 (anonymous) @ npm.angular.bundle.js?v=4768:18 dispatch @ jquery-3.6.0.min.js?35212621148:2 (anonymous) @ jquery-3.6.0.min.js?35212621148:2 npm.angular.bundle.js?v=4768:10 POST https://developer.apple.com/services-enrollment/getCaptcha 401 (Unauthorized) i think the page is broken? even if you use the audio its not working. started on 5 juni with DUN and did have 4 calls and also multiple emails and still it is not solved and i cannot proceed. im not so happy that i do not get HELP so now here. i hope that someone can help? i cannot stop the migration, no buttons to cancel or to change. please help me?

Hi everyone, Has anyone experienced a similar issue with an Apple Developer Program membership renewal? On July 20, 2026, I received an email from Apple confirming that my membership had been successfully renewed until July 20, 2027. My credit card also showed a charge from APPLE.COM, which matches the Apple Developer Program membership fee. However, eight days later, I received another email saying that Apple was unable to collect the payment after several attempts, and my Apple Developer Program access was disabled. I’m confused because: Apple previously confirmed that the renewal was successful. The membership expiration date was updated to July 20, 2027. My credit card shows a transaction from APPLE.COM. And And I contacted the bank that issued my credit card. They said Apple hasn't sent a bill for this purchase. So I have tried to enroll but website display "Sorry, you can’t enroll at this time. Your Apple Account is already associated with the Account Holder of a membership." Any advice from someone who has experienced this would be greatly appreciated. Thank you.

Hey there, About 2 weeks ago I enrolled in the apple developer program and ive been waiting for it to be approved. My app is ready and this is keeping me behind schedule for my release. Could someone help me resolve this. I emailed and sent tickets but nada. Thank you

I have a project that builds fine in macOS 26 with Xcode 26. On macOS 27 b4 and Xcode beta, the same project can't build because of a framework that should be pulled from a Swift Package from a package-registry (named Registry, for example below), hosted on JFrog. I have the registry set up and have the token in keychain. The resolution of the packages works. But when I build, I get error like this: error: Missing package product 'Registry.Package_Package.Package' (in target 'Target' from project 'Project') . The real package should just be 'Registry.Package'. Any help with that? Is it a bug?

Hi Developer Team, My developer account is asking to enroll even though im already a member of an organization so when i click enroll it says ive already enrolled which is correct, but when i go to account, its syaing i need to enroll. I have an active subsription and everything is up to date. except this thing thta is asking i enroll even though im already enrolled. Please fix this issue. I have reached out to the team via the support but no response since Early April. Could you please look into this and fix. im unable to access the developer account as a result of this.

Xcode 27 beta 4: how do I create a local package for my project? The menu path File > New > Package no longer exists.

Hi There, I am unable to renew apple developer program membership this year as there is a restriction to renew the account using Apple developer app using only iPhone / MacBook. Error pop-up : your purchase could not be completed / unknown error occurred.

I've been unable to access my Apple certificates for four months. I reported this to Apple Developer Support, but they say they don't know the reason and are investigating. My developer subscription expires in a few months, and the money I paid and the time I lost will be wasted. I contacted the support team again today, and they say they've been investigating for four months. I've decided to take legal action. What steps should I take?

Team ID XRTVVR644Y We have the case number mentioned above in limbo. The ticket has been escalated over 2 months (May 2026) without any updates. We are currently locked out of our Developer account and have had certificates expire since then, as well as need to publish some apps for clients. We are asking for someone to manually review this case and get back to the primary email address on our account.

Hi, I'm trying to understand how the external purchase token reporting flow is supposed to work. The documentation says: At launch and before every potential transaction, call the token(for:) function to request the external purchase tokens, using the token types ACQUISITION and SERVICES. Associate these tokens with a customer account on your server. Doc In another article, Apple says: To send a report, call the Send External Purchase Report endpoint for each token. Send reports in all of the following cases: To report a token, with line items, when a customer completes one or more transactions. To report a token, without line items, when a customer doesn’t complete any transactions. To report an unrecognized token, when you receive an App Store Server Notification about a token that you don’t have recorded in your system. To report duplicate ACQUISITION and SERVICES tokens. Doc I'm having trouble reconciling these requirements and would appreciate some clarification. My questions are: If I receive ACQUISITION and SERVICES tokens at app launch, but the user never attempts a purchase, should I eventually report those tokens without line items (case #2)? If so, when should that report be sent? If a user starts the purchase flow but abandons it (for example, closes the browser or cancels payment), should that token be reported without line items under case #2? If I receive a new SERVICES token that covers the same validity period as a previously stored token, should it be treated as a duplicate and reported immediately under case #4? Should I still store that token on my server? The documentation says to call the Send External Purchase Report endpoint "for each token." Does that mean every transaction must be reported against all relevant tokens, or only against the specific token associated with that transaction? An end-to-end example of the expected token lifecycle (request → store → use for transactions → report) would be very helpful. Any guidance or examples of the intended workflow would be greatly appreciated.

Hi everyone, We recently renewed and successfully paid for our Apple Developer Program membership. However, our account is still showing as expired, and we're unable to access the developer services that require an active membership. We've already completed the payment, but the membership status has not updated yet. Has anyone experienced this issue before? How long did it take for your membership to become active after payment? Is there anything we need to do, or is this just a delay on Apple's side? Should we contact Apple Developer Support, or will the status update automatically? Any advice would be greatly appreciated. Thank you!

With Xcode Version 26.5 (17F42) apps can no longer be launched on a real Vision Pro once migrated to visionOS 27 Beta 2. At launch there is an EXC_BAD_ACCESS runtime error in an initialiser. If you launch apps on a real iPhone/Ipad with OS 27 Beta 2 the program will stop before the end of its start, but there is no precise line with the error. Xcode just stop in assembly code in the debugger, in the init phase of Swift where it searches for which objects to instantiate at launch. After investigating, the error comes from a debug setting from Xcode to show the stack trace. To avoid the error when run from Xcode Version 26.5 (17F42) In Xcode, open Product > Scheme > Edit Scheme. Select the Run action in the sidebar, then open the Options tab. Find Queue Debugging and uncheck Enable backtrace recording. If Queue debugging is enabled, then the program crashes when launched It is useful to be able to run apps from the production Xcode to devices with 27 OSes in beta to be able to test that everything will work fine for new versions of apps released before OSes 27 release. Thank you A previous post was made but the cause was badly identified. New Feedback including a sample code FB23384318

Due to massive amount of shared state in my project I cannot really use swift testing parallelization in my tests, so my idea was to embed all suites into single one with .serialized and then run them on several simulators to speed up the tests. I ran tests with xcodebuild ... -parallel-testing-enabled YES -parallel-testing-worker-count 2, but swift testing suites seemed to be executed on just one simulator. Is it possible to run swift testing tests in parallel on multiple iOS simulators, but serially within each of them? Or the only way is xctest?

Where did the simulator "Slow animations" mode go? I can't find it in the Xcode 27 beta 2 "Device Hub". This feature is incredibly useful. I'm assuming it's a glitch that it's missing, or I'm just not looking in the right place.