I wonder if there’s an issue with ASC. Since last week, I get this warning when syncing my sale figures with AppFigures:  »[Apple ID] has new terms to agree to in App Store Connect. We will try to continue importing but some data may not be available. Please log in to your App Store Connect account and accept the Terms & Conditions. » However, all agreements are marked as active.

This is unacceptable, Apple. How are we supposed to run a business and take proper care of our users when App Review times have deteriorated to this extent? If an influx of low-effort, AI-generated apps is overwhelming the review process, then perhaps it’s time to introduce a higher-tier “Pro” developer membership — one that ensures established, legitimate businesses can continue operating without being penalized by systemic delays.

Hi Albert, Thanks for the clarification. In past cycles, RC builds have typically been permitted for submission within a few hours, so this situation is a bit unusual. I’m assuming iOS 26.2 will likely ship next week, but ASC is also warning developers that they may be overwhelmed during the holidays and encouraging early submissions — which puts us in a difficult position when RC uploads aren’t yet allowed. Being able to submit with the RC would let us validate TestFlight builds ahead of time and ensure a smooth transition once 26.2 is released. At the moment, it isn’t even possible to test distribution builds, which makes it hard to prepare properly. Could you shed some light on why RC submissions are blocked this time around? Thanks again for your help.

So I finally got it to work. Here's what I did (no idea if all of these were required): Signed out from App Store Connect in Safari Cleared all *.apple.com website data Restarted The "Get" button finally appeared in Components. On my other Mac, signing out and closing Safari fixed the issue.

It's been 20 minutes on my end and still nothing...

I have the same issue at the moment with Xcode 26 beta 3. Neither iOS or visionOS will download. Did restart my Mac and relaunched Xcode several times.

Same issue. Have you been able to find a solution?

Same issue here.

Still an issue with macOS 26 beta 1 (25A5279m) and Xcode 26 beta 1 (17A5241e). At this point I assume this will never get fixed.

Still an issue with macOS 26 beta 1 (25A5279m) and Xcode 26 beta 1 (17A5241e). At this point I assume this will never get fixed.

Still an issue with Xcode Version 16.3 beta 2 (16E5121h) and macOS 15.4 Beta (24E5222f).

Still an issue with Xcode Version 16.3 beta 2 (16E5121h) and macOS 15.4 Beta (24E5222f).

Still not fixed in macOS 15.3 (24D60). FB15513599 import SwiftUI struct ContentView: View { @State private var showEditItem = false var body: some View { VStack { VStack { Text("Instructions to reproduce the crash") .font(.title) .padding() Text(""" 1. Click on "Toggle Item" 2. In the menu go to File > New Window 3. In new window, click on "Toggle Item" """) } .padding() Button { showEditItem.toggle() } label: { Text("Toggle Item") } } .padding() .toolbar(id: "main") { ToolbarItem(id: "new") { Button { } label: { Text("New…") } } if showEditItem { ToolbarItem(id: "edit") { Button { } label: { Text("Edit…") } } } } } }

Still not resolved in 15.3RC (24D60). Like the SwiftUI engineers, I’m giving up. I’ll leave it to users who want customizable toolbars to contact Apple instead.

Still experiencing this issue with macOS 15.3 Beta 3 (build 24D5055b). I guess Apple’s focus has shifted to promoting TV shows and generating bogus news summaries, rather than addressing bugs in features that have been part of macOS since its inception 24 years ago. So much for “the modern way to build apps is SwiftUI” slide in a recent WWDC video...