FWIW, the macOS version of my app was finally approved last night. It remained roughly 48 hours "In Review".

Same here. Our iOS and visionOS submissions were approved within a few hours, while the macOS submission has now been “In Review” for nearly 48 hours. At this point, we’re also seriously considering offering a direct version of the Mac app so we’re not entirely dependent on the Mac App Store review process.

@iTen I’m on the same boat. Both iOS and visionOS submissions were approved within a few hours but the macOS version is sitting in review for close to 48 hours, despite requesting an expedited review, which was granted but nothing has moved yet. At this point, I’d rather get a rejection for which I could take action instead of just sitting there.

@Etresoft Yes, I’m using new APIs specific to the OS 27 releases. Supporting the OS and adopting its new APIs are two different things. In any case, I think we’ve exhausted this discussion. My point remains that an app sitting “In Review” for days creates unnecessary uncertainty for developers trying to coordinate releases around a new OS launch. We clearly disagree on that, so I’ll leave it there.

@Etresoft If you’re implying that my app might be a scam, I think nearly 16 years on the App Store with an established product and track record provides some useful context. As for submitting earlier, I submitted as soon as Apple began accepting apps built with the tools required to support macOS 27. I’m not sure what more preparation would have changed here. My point isn’t that reviews shouldn’t happen. It’s that once an app enters “In Review,” leaving it there for days with no predictable timeline makes release planning unnecessarily difficult for legitimate developers.

Can't sign in with Pro account in neither Xcode 26 or 27. Tried all the workarounds in the thread, nothing works. This was fine until this morning.

I haven't been able to sign in since this morning. Even though the sign-in appears successful, Xcode still shows me as "Not Signed In." This is occurring in both Xcode 26 and 27. I know there are some ongoing issues on OpenAI's end at the moment, so I might just be one of the affected users.

I haven't been able to sign in since this morning. Even though the sign-in appears successful, Xcode still shows me as "Not Signed In." I know there are some ongoing issues on the OpenAI end at the moment, so I might just be one of the affected users.

If you embed your view in another view, for example a VStack, then the crash no longer occurs: VStack { if #available(iOS 26.0, macOS 26, *) { Text(task.title) .frame(maxWidth: .infinity) .padding() .background(.blue.opacity(0.1)) .clipShape(.rect(cornerRadius: 12)) } else { Text(task.title) .frame(maxWidth: .infinity) .padding() .background(.blue.opacity(0.1)) .clipShape(.rect(cornerRadius } }

Would be nice to hear from an Apple engineer about this.

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