Overview

Hi everyone, and @Apple Developer Support, I'm posting here because I've exhausted the other support channels (the phone callback isn't working and the email form returns "a problem occurred while processing your request"), and I've read that this forum is where the support team is most responsive. I enrolled in the Apple Developer Program and paid the annual membership fee, but my account has been stuck on "Pending" for nearly a month with no activation and no confirmation email. To make it worse, when I open my account, the page still shows "Complete your purchase" with a "Continue to payment" button — as if I had never paid — even though the $99 was already charged to my card. I have NOT paid a second time, to avoid a duplicate charge. Here are my details: Enrollment ID: 7X64GZX28W Apple Support Case ID: 102895927935 Full name: Deiwidy Maziero Account type: Individual Payment date: May 14, 2026 Payment method: credit card Amount: $99.00 Region: Brazil (I'm not posting my account email publicly — happy to provide it privately to Apple Support.) What I have already verified: The $99 was charged/confirmed on my credit card I am using the same Apple ID that was used for the enrollment I checked my inbox and spam folder daily — no emails from Apple I have NOT made a duplicate payment It has now been almost four weeks, far beyond the stated 48-hour processing time, and this is blocking my work. I'm formally requesting manual intervention from Apple staff to: Review and activate my Apple Developer Program enrollment Reconcile my confirmed payment with the enrollment, since the page still asks me to complete a purchase I have already paid for Explain what is keeping the enrollment in "Pending" status If anyone from the community has faced this same situation (paid, but the page still asks to complete the purchase) and found a fix, I'd really appreciate your input. I'll keep this thread updated. Please boost so it gets visibility. Thank you.

I can't use cloud-based AI providers, so I'm very excited about the potential of local models with Xcode's Coding Assistant. I've been playing around with a local MLX model, and have been generally pretty satisfied with it. But I'm curious - what features am I missing out on by using a local model instead of a larger, cloud-based model? Is Xcode's ability to run tests, build the project, etc. limited by the use of a local model? Does it limit the ability to do more complex agentic workflows? If so, how? Basically, local models in Xcode seem to be working pretty well for me, and I'm curious to know what cloud-based models can offer that I don't already have.

In the video "Xcode, Agents and You" (direct link), the presenter asks for a walkthrough of the open project and Xcode presents a rich-text overview of the app's architecture, with color-coded diagrams and clickable links to the files it discusses. I can't get that to work when I try it, though. Is this a preview of a feature that isn't yet available in the first beta of Xcode 27? Is this because I'm using a local model or because it only works with a specific kind of model?

In the recent SwiftUI Group Lab, they mentioned using Dynamic Property instead of onChange, How to do it? Could it used as an actual property type instead of just using in combination with @propertyWrapper

Does this API only work for inference running on the GPU? If the inference runs on the ANE, can I still use this API? I noticed that the commandQueue parameter is an MTLCommandqueue? https://developer.apple.com/documentation/coreai/computestream/init(commandqueue:)

so the app is free to download . the first use is free for two days . We want to send a reminder to them via email. some are installing (67%) but not returning to use the free credit. what is the policy on getting the apple id from apple. do we have to ask the user for the id at install and then disclose that its for tracking purposes and to inform about future promo's . the id will not be shared with third parties

I couldn't decide whether to post this question here or in SwiftUI Q&A as there's a lot of overlaps. We're trying to create something similar to UIViewRepresentable for UIKit. This might not work for complicated cases where the View has many pieces but as long as it works for simple cases, we're happy. The only problem right now is figuring out the correct height. Currently, the height anchor is assigned to CGFloat.greatestFiniteMagnitude, which works but when inspecting the layout in View Hierarchy, it appears the wrapped view is getting stretched all the way down. Also, sometimes View Hierarchy isn't able to draw the wrapped View and I'm unsure if it's a problem of View Hierarchy or our implementation. final public class SwiftUIConfigurationContainerView<T: View>: UIView { private var contentView: UIView? public override var intrinsicContentSize: CGSize { contentView?.intrinsicContentSize ?? super.intrinsicContentSize } private var preferredContentSize: CGSize? public init(@ViewBuilder _ content: @escaping () -> T) { super.init(frame: .zero) setUpContentView(content) } @available(*, unavailable) required init?(coder: NSCoder) { return nil } private func setUpContentView(_ content: @escaping () -> T) { let contentView = UIHostingConfiguration { [weak self] in VStack(spacing: .zero) { content() .onGeometryChange(for: CGSize.self, of: \.size) { size in self?.preferredContentSize = size self?.invalidateIntrinsicContentSize() } .frame(maxWidth: .infinity, alignment: .center) Spacer(minLength: .zero) } } .minSize(width: .zero, height: .zero) .margins(.all, .zero) .makeContentView() self.contentView = contentView addSubview(contentView) contentView.translatesAutoresizingMaskIntoConstraints = false NSLayoutConstraint.activate([ contentView.leadingAnchor.constraint(equalTo: leadingAnchor), contentView.trailingAnchor.constraint(equalTo: trailingAnchor), contentView.topAnchor.constraint(equalTo: topAnchor), contentView.heightAnchor.constraint(equalToConstant: CGFloat.greatestFiniteMagnitude), ]) } }

Hello, I am posting here in the hope that someone from the Apple Developer Program team can review and escalate my case, as I have been unable to get any response through the standard support channels. Summary of my situation: Enrollment type: Organization (EleveNode LLC) Enrollment ID: Z7S59G8HV5 Enrollment submitted: April 29, 2026 Case ID: 102881713619 D-U-N-S number: Active and correctly linked to the organization Timeline of what happened: I submitted the required documents. I then received a message from Apple requesting additional documents. I uploaded all the requested documents. The enrollment was rejected, with no reason given. Since then, I have contacted Apple Developer Support three times (May 19, May 25, and June 7) to understand the reason for the rejection and how to resolve it. None of these messages have received a reply. For context: I have successfully completed Apple Developer Program enrollment twice before, once with my personal individual account, and once with another business entity both without any issues. At this point, I have not been told what documentation was insufficient, what verification failed, or whether there is anything further required from me. The phone/callback support option is not available in my region, so the contact form is my only channel, and it is not producing any response. This is blocking my ability to publish apps under my company and is affecting my business commitments. I would greatly appreciate it if an Apple representative could review my case and escalate it to the Developer Program Enrollment team, or at minimum tell me the reason for the rejection so I can address it. Thank you for your time and assistance. Adam

I'm seeing a regression in SwiftUI Charts on iOS 27 beta 1. Any view placed inside a BarMark's overlay annotation no longer receives the size of the parent BarMark. It collapses to zero, so any content sized from geo.size (e.g. a Rectangle meant to fill the bar) renders empty or incorrectly. Expected: The GeometryReader reports the BarMark's rendered width/height, and the Rectangle fills the BarMark (this is the behavior in iOS 26 and earlier). Actual: On iOS 27 beta 1, geo.size is effectively zero, so the overlay content has an extremely small size. I suspect this could be a small bug with the new ContentBuilder / ViewBuilder changes but that's just a hunch. Here's a code sample which reproduces the issue. // MARK: - Mock Data Models struct ScheduleSeries: Identifiable { let id = UUID() let data: [ScheduleItem] } struct ScheduleItem: Identifiable { let id = UUID() let startDate: Date let startHour: Double let endHour: Double let secondaryText: String? } // MARK: - Minimal Reproducible Example struct ContentView: View { // Generate two consecutive days for the mock data let mockSchedule: [ScheduleSeries] = [ ScheduleSeries(data: [ ScheduleItem( startDate: Date(), startHour: 9.0, endHour: 11.5, secondaryText: "Morning Event" ), ScheduleItem( startDate: Calendar.current.date(byAdding: .day, value: 1, to: Date())!, startHour: 13.0, endHour: 16.0, secondaryText: "Afternoon Event" ) ]) ] var body: some View { VStack(alignment: .leading) { Text("FB: Annotation Sizing Bug") .font(.headline) .padding(.bottom, 8) Text("Expected: The gray Rectangle should stretch to fill the BarMark.\nActual: GeometryReader/Annotation fails to size to the parent BarMark.") .font(.caption) .foregroundColor(.secondary) .padding(.bottom) Chart(mockSchedule) { series in ForEach(series.data, id: \.startDate) { element in BarMark( x: .value("Day", element.startDate, unit: .day, calendar: .current), yStart: .value("Start", element.startHour), yEnd: .value("End", element.endHour), width: .ratio(0.99) ) .annotation(position: .overlay, alignment: .topLeading) { item in ZStack { VStack(alignment: .leading, spacing: 0) { // BUG DEMONSTRATION: // This GeometryReader and Rectangle previously filled the BarMark, but in Xcode 27 it does not GeometryReader { geo in Rectangle() .fill(Color.black.opacity(0.15)) .frame(width: geo.size.width, height: geo.size.height) } } .foregroundColor(.white) .font(.caption2) } } } } .chartYScale(domain: 0...24) // Lock the Y-axis to a 24-hour scale } .padding() } } Environment: Xcode 27 beta 1 / iOS 27 beta 1 Reproduces on device and Simulator Worked as expected on iOS 26 and earlier Here's what the issue looks like in our app with zero code changes: iOS 26 iOS 27 I've filed a feedback report (FB23016343) with a sample project attached. Has anyone else hit this, or found a workaround for sizing overlay annotation content to a BarMark in iOS 27? Thanks!

I submitted an update to my app, which is a critical update to address some bugs. The submission has been In Review for over 43 hours. Is this normal?

My update has been in "waiting for review" for over 2 weeks now, even for the TestFlight version.

This idea is based on a few key points: GNU Coreutils has essentially become the de facto standard with the widespread adoption of GNU/Linux. Apple has been attracting modern developers by being 'Linux-like' (via POSIX-compliant), especially since Linux has largely won the race in the general-purpose Unix-like OS space. Adopting uutils would allow scripts to run much more seamlessly across macOS and Linux. uutils is compatible with GNU Coreutils, and its MIT license avoids the strict restrictions associated with GPLv3. By aligning base commands more closely with Linux, I think this would give macOS another compelling advantage over WSL2 for developers.

Hi everyone, I'm trying to enroll in the Apple Developer Program, but every time I attempt the payment it fails and shows a message asking me to contact support. I've waited the suggested timeframe and retried, but the payment still won't go through. This is blocking me from completing enrollment and setting up App Store Connect. What I've already tried: Retried the payment after the recommended waiting period — same error Emailed Apple Support (case number: 102911809145) — no response so far Tried calling — the phone/"Call Me" callback option that was previously available has now been removed from my Contact Us page At this point I have no working way to reach Apple Support directly. Has anyone run into this same payment error during enrollment? If so, what finally resolved it for you? And if any Apple staff see this, I'd really appreciate help getting case 102911809145 looked at. Thanks in advance.

I have a universal app available on both iOS and macOS. The macOS version appears in App Store search results and can be found normally. The iOS version has been approved and is available for download via its direct App Store link, but it does not appear in App Store search results when searching by app name. This is my first App Store release, so I’m not sure whether this is a normal indexing delay or a configuration issue. Information: Platform: iOS and macOS Direct App Store links work for both versions macOS version is searchable iOS version is not searchable Is there anything in App Store Connect that I should verify, or is there a typical delay before a newly released iOS app becomes searchable? Thank you for any guidance.

Hi, I joined the New Siri waitlist on June 8 (the day of WWDC 2026) and as of June 12, I have still not been granted access on iPhone or iPad — that's 4 days with no activation. I used the Terminal workaround on macOS 27 Golden Gate Beta (EnhancedSiriWaitlist → Enabled = NO), which successfully activated New Siri on my Mac. However, it has not synced to my other devices despite being on the same Apple ID with iCloud Siri sync enabled. Device details: Mac mini (macOS 27 Golden Gate Beta) — New Siri active ✓ iPhone (iOS 27.0 Developer Beta 1) — Joined Waitlist since June 8 iPad (iPadOS 27.0 Developer Beta 1) — Joined Waitlist since June 8 Steps already attempted: Multiple restarts on iPhone and iPad Toggled iCloud Siri sync off/on Toggled Siri off/on multiple times iCloud storage sufficient (200GB plan, 53GB used) 4 days seems far beyond normal rollout time. Is this a known issue? Is there anything on the account side that could be blocking activation? Thank you.

Are there any plans to allow wifi-only Apple TV 4K units to be manually enrolled into ASM/ABM like we can do with every other device/OS? I have several that were purchased as gifts but we can not use them as they need to be manually added to ASM. However, it's not yet possible.

When I opened an Intel-based app in the macOS 27 beta, a prompt informed me that apps requiring Rosetta will not work in the next OS release (macOS 28). It also prompted me to install Rosetta to continue using the app in macOS 27. After installing, I began wondering if there is a way to remove Rosetta via Settings. Since it is now treated as an optional feature, shouldn't we be able to uninstall it similar to how command line tools are managed? Does anyone know of a method to completely remove Rosetta once it has been installed? (PS: This post was rewritten using Siri AI)

I have been waiting for ios27 siri since 5 pm monday its Friday now im still waiting

I started enrolling in the Apple Developer Program last Sunday. The confirmation email said I should receive a response within two business days, but it's now been five days and I still haven't heard back. Is this normal?

Hi everyone, I'm working on a Live Activity implementation for a ticketing app (written in Swift/SwiftUI with ActivityKit), and I've encountered an unexpected behavior on iOS 26.2.1 that contradicts my understanding of the documentation. What the docs say: The official ActivityKit documentation states: "The system uses the minimal presentation when more than one app has an active Live Activity." This implies the two minimal slots are intended for two different apps. There is no documented scenario where a single app occupies both minimal positions simultaneously. What I observed: On a device running iOS 26.2.1, with two active Live Activities from the same app running at the same time, both minimal views appeared on the Dynamic Island simultaneously — one attached to the island, one as a detached floating pill. Questions: Is this behavior intentional in iOS 26, or is it a regression / unintended side effect? Has the system policy changed in iOS 26 to allow a single app to occupy both minimal slots? If this is expected, is there any updated documentation or release notes that cover this change? Environment: Device: iPhone 14pro iOS: 26.2.1 Xcode: xcode26 Any insights from Apple engineers or developers who've seen this would be greatly appreciated. Thanks!