Dear Apple Support Team, I am writing to formally escalate an unresolved membership activation issue that has persisted despite multiple support requests submitted through the official channels. I kindly request your urgent attention to this matter. ISSUE SUMMARY I placed an order for an Apple subscription/membership under Order Number W1360969504. However, following the successful completion of the payment, my account was never activated. The membership remained in a pending state with no resolution. PREVIOUS SUPPORT ATTEMPTS In an effort to resolve this issue, I contacted Apple Support on two separate occasions: Support Case ID: 30000002928955 Support Case ID: 102851903923 Unfortunately, neither of these cases received a response from the support team. Due to the continued inactivity of my account and the complete absence of follow-up communication, I was left with no option but to cancel the membership myself. SECOND ENROLLMENT ATTEMPT Following the cancellation, I re-applied for the membership. The new order was processed and payment was completed successfully: New Order / Invoice Number: W1638536754 However, this second enrollment is experiencing the exact same issue. My account has again failed to activate, and I am continuously presented with the following error message: "To continue your enrollment, complete your purchase now" This error appears despite the payment having been processed, which suggests a backend activation failure on Apple's side rather than an issue with my payment method or account credentials. CURRENT STATUS Two payments processed — membership never activated on either occasion Two prior support requests submitted — no response received Persistent enrollment error blocking any progress Account remains inactive as of the date of this email REQUESTED ACTION I kindly ask that your team: Investigate both orders (W1360969504 and W1638536754) and identify the root cause of the activation failure. Review and respond to the previously submitted support cases (#30000002928955 and #102851903923). Manually activate my membership Provide written confirmation of the resolution steps being taken. Given that this issue has already caused significant delay and inconvenience, I would greatly appreciate a response within 24–48 hours. Thank you for your time and assistance. I look forward to a prompt and satisfactory resolution. Sincerely, Miraç Bahadır Öztürk March 30, 2026

I enrolled for the Apple Developer Program last Thursday (Feb 12) - no status update apart from a message I've seen others have thus processed payment: Purchase your membership. To continue your enrollment, complete your purchase now Your purchase may take up to 48 hours to process. I've reached out to support twice now, no luck. Anything that worked for someone in the same boat? I have a test group planned and would need to apply my app for testflight as soon as possible to leave some headroom.

I'm trying to download the iOS 26.2 simulator, but it fails both in Xcode and via the command line. When I run: xcodebuild -downloadPlatform iOS -buildVersion 26.2 -exportPath ~/Downloads It returns: iOS 26.2 is not available for download. I would like to know: Why iOS 26.2 simulator cannot be downloaded at the moment. Whether iOS 26.2 simulator is still available, or if it has been removed or replaced. How to properly get and install the iOS 26.2 simulator. Any official explanation or solution would be greatly appreciated. Thank you!

I am experiencing a UI issue after migrating my app from Xcode 16 to Xcode 26. In my implementation, I have a toolbar that contains multiple buttons along with a dropdown menu. The hierarchy for dropdown is as follows: **Toolbar → ToolbarItem → View → Menu → Picker ** Prior to Xcode 26, this setup worked smoothly in production builds. The dropdown (Menu + Picker) behaves as expected, and selecting a value triggers loading a dataset containing thousands of records on the screen. However, after upgrading to Xcode 26, I am observing an animation glitch when dismissing the dropdown after a selection is made. Specifically, the dropdown briefly shows a “capsule-like” animation artifact during dismissal, which persists for a few seconds. This visual issue is noticeable and negatively impacts the perceived performance and user experience of the app. This issue is occurring in an already released app built with Xcode 26. Questions: Is this a known issue or regression in Xcode 26 / SwiftUI Menu or Picker components? If yes, are there any known fixes or upcoming Xcode versions where this is resolved? If not, what would be the recommended approach to eliminate or minimize this animation glitch when dismissing the dropdown? Additional Context: The issue appears only after migration to Xcode 26. The dataset loaded after selection is large (thousands of records). The glitch specifically occurs during the dismissal animation of the Menu/Picker. Any guidance or workarounds would be greatly appreciated.

For difficult reasons I won’t get into, I ended up manually downloading the latest iOS 26 simulator runtime. I now have a file named 78756498-8AB4-4E5A-986C-7AA435758657.aar copied to my Mac. How do I get this archive installed so Xcode 26 recognizes it as a proper simulator runtime component? All searching I‘ve done for manually installing simulators references dmg files and older versions of Xcode. There’s no mention of aar files. When I tried the command: sudo xcrun simctl runtime add ./78756498-8AB4-4E5A-986C-7AA435758657.aar I get the result: An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=22): Error while creating AEA backend Invalid argument I tried to use Archive Utility to open the file but that just says it is unable to expand the file. I even tried renaming the file with a dmg extension and then tried mounting the file and I get the same “AEA backend” error. My Mac doesn’t have sufficient Internet access to let me download and install this normally through Xcode. I need to find a way to get this file installed manually.

When I was reading a topic written by somebody, suddenly, the web browser (Safari) directed me to this Unauthorized error page. What the hell is this, Apple, Inc? It seems that things are quite chaotic about what Apple, Inc. does these days. I hope they will manage to sort things out.

Hello Apple Developer Community, I'm seeing a persistent crash in my iOS app reported via Firebase Crashlytics. The issue only started appearing on devices running iOS 26.3.0 and above (the crash does not occur on lower iOS versions, and it's unrelated to my app's version number). Key points: My app does NOT use any Text-to-Speech (TTS) features whatsoever. No AVSpeechSynthesizer, no Speech framework, no related APIs called from our code. My app is primarily written in Objective-C (with some Swift components possibly via dependencies). The crash stack is entirely within Apple's private TextToSpeech framework, specifically in ausdk::BufferAllocator::instance(). I suspect it might be indirectly triggered by a third-party ad SDK (e.g., Google Mobile Ads, AppLovin, etc.) that could be loading or interacting with accessibility features in the background — but this is just a hypothesis, as I have no direct evidence yet. Here is one representative crash log: Crashed: com.apple.root.user-initiated-qos.cooperative 0 TextToSpeech 0x6bb00 ausdk::BufferAllocator::instance() + 99800 1 TextToSpeech 0xf8c60 ausdk::BufferAllocator::instance() + 677688 2 TextToSpeech 0xf8c60 ausdk::BufferAllocator::instance() + 677688 3 TextToSpeech 0x1a0b9c ausdk::BufferAllocator::instance() + 1365620 4 libswift_Concurrency.dylib 0x628b4 swift::runJobInEstablishedExecutorContext(swift::Job*) + 288 5 libswift_Concurrency.dylib 0x63d28 swift_job_runImpl(swift::Job*, swift::SerialExecutorRef) + 156 6 libdispatch.dylib 0x13f48 _dispatch_root_queue_drain + 364 7 libdispatch.dylib 0x146fc _dispatch_worker_thread2 + 180 8 libsystem_pthread.dylib 0x137c _pthread_wqthread + 232 9 libsystem_pthread.dylib 0x8c0 start_wqthread + 8 The crash occurs on a background cooperative queue (Swift Concurrency). Questions: Has anyone else seen crashes inside ausdk::BufferAllocator::instance() in TextToSpeech on iOS 26.3.0+ even without using TTS in their app? Could a third-party ad SDK be causing the TextToSpeech framework to load unexpectedly (e.g., via accessibility preloading)? Is this a known bug in iOS 26's Spoken Content / Speak Selection features? Any workarounds or fixes from Apple? Any insights, similar reports (especially from Objective-C based apps), or advice would be greatly appreciated! Thanks!

Currently all Feedback Assistant IDs on the Apple Developer Forums are links even if the user does not have access to them. It could be helpful if they were only linked when the signed in user has access to them. FB22353186 https://github.com/feedback-assistant/reports/issues/786

I just leave my developer team from Apple Developer Program,and re login,can see nothing. But when I get into https://developer.apple.com/ and login,still can see my team information. And I check the team information, the account holder is not me . WHY retain this question?

Trying out the new package trait support in Xcode 26.4 and it seems like the default traits for the package are being enabled even when explicitly set to disabled. At first I thought it was something wonky in the Xcode UI around the new support for traits. I've been able to replicate the issue with just two Swift packages, so no Xcode UI for setting the traits. Feature package // swift-tools-version: 6.3 import PackageDescription let package = Package( name: "MyAwesomeFeature", platforms: [ .macOS(.v26) ], products: [ .library( name: "MyAwesomeFeature", targets: ["MyAwesomeFeature"] ) ], traits: [ .trait(name: "SomeBetaFeature"), .default(enabledTraits: ["SomeBetaFeature"]), ], targets: [ .target( name: "MyAwesomeFeature" ), ], swiftLanguageModes: [.v6] ) For the sake of testing I've given it a simple object that just prints if the trait is enabled Inside MyAwesomeFeature public struct SomeObject { func printTraitStatus() { #if SomeBetaFeature print("Beta feature enabled") #else print("Beta feature disabled") #endif } } I then have a second package that depends on the feature and produces an executable // swift-tools-version: 6.3 import PackageDescription let package = Package( name: "SwiftPackageBasedProgram", platforms: [ .macOS(.v26), ], products: [], dependencies: [ .package(name: "MyAwesomeFeature", path: "../MyAwesomeFeature", traits: []) ], targets: [ .executableTarget( name: "MyAwesomeProgram", dependencies: [ .product(name: "MyAwesomeFeature", package: "MyAwesomeFeature") ] ), ], swiftLanguageModes: [.v6] ) If I run MyAwesomeProgram from the command line with swift run I get the output I would expect Build of product 'MyAwesomeProgram' complete! (6.10s) Inside SwiftPM program Beta feature disabled If I run the same program from within Xcode though Inside SwiftPM program Beta feature enabled Program ended with exit code: 0 I've got the sample project available here if anyone wants to try it out. Has anyone else come across anything like this? Very possible I'm just missing something.

Hello, it's been 14 days since we applied for an Apple Developer account for our company, and it's still not active. We've sent three emails, but haven't received a single reply. Has anyone else experienced this problem?

I've been investigating a persistent 401 Invalid Bearer Token error with Claude Agent in Xcode 26.3 on an Intel Core i9 Mac and wanted to share my findings here in case others are affected. ENVIRONMENT Hardware: Intel Core i9 (x86_64) Xcode: 26.3 (17C529) macOS: 26.3 (25D125) THE ISSUE Claude Agent fails with "Failed to authenticate. API Error: 401 - Invalid bearer token" on every prompt, despite the account showing as Signed In under Settings → Intelligence. The error persists after signing out and back in, and the token is confirmed valid and unexpired in Keychain. WHAT WORKS Claude Code in Terminal works perfectly on the same machine with the same credentials The basic Claude Sonnet 4.5 coding assistant in Xcode works fine Only Claude Agent is affected ROOT CAUSE HYPOTHESIS Xcode appears to be installing an ARM64 Claude binary on Intel Macs silently, with no warning or fallback. This binary likely fails to execute on x86_64 hardware and that failure is being misreported upstream as a 401 authentication error — which is why the error has nothing to do with the actual credentials. APPLE'S RESPONSE Feedback report FB22141224 was closed as 'Works as currently designed' with the explanation that Claude Agent requires the Neural Engine found on Apple Silicon. However, Claude Agent calls Anthropic's remote API over the network and performs no on-device AI processing — the Neural Engine is not involved. The fact that Claude Code works fine on this same Intel Mac with the same credentials demonstrates this clearly. WORKAROUND Using an Anthropic API key instead of OAuth resolves the issue but requires additional paid billing outside of an existing Claude.ai subscription. Has anyone else experienced this on either Intel or Apple Silicon? I'd be particularly interested to hear if Apple Silicon users are also affected, as the Developer Forums suggest this may not be limited to Intel Macs (thread/816369). Any input from Apple DTS engineers would be greatly appreciated.

Guys I signed up for Developer Account over a week ago. There is no any email that I received only the order id and the receipt. When I log in to my developer account It shows me like I am not paid or registered but in my back account I saw that I paid. So what's wrong with that why am I still waiting for confirmation?

Hello 👋 I would like change my username for several reason. Is there a way to change it ? I don’t want to create an another Apple account just for that. Have a nice day 😁

Hi everyone, I’m reaching out to see if anyone has found a fix for a stuck Apple Developer enrollment. I recently joined my company and need to get our environment ready, but I’m hitting a wall. The Timeline: Enrolled: Monday, March 23. Confirmation: Received the "2 business days to process" email. Current Status: My profile still says "Pending." The Issues: The portal gives me an option to "Complete enrollment by purchasing," even though I already did. Although the checkout showed "Success" at the time, no charge has appeared on my bank account yet. I’ve contacted Apple Support twice with no response so far. I’ve seen others mentioning similar issues lately. Has anyone managed to bypass this "Pending" loop without double-paying? Should I just keep waiting, or is there a specific support channel that actually responds? Thanks in advance for any insights!

Using XCUITesting to access images using photos picker. The code is roughly like this: photoPickerButton.click() try await Task.sleep(for: .seconds(2)) let images = app.descendants(matching: .image) .matching(identifier: "PXGGridLayout-Info") // select the first 5 images for ix in 0..<5 { let image = images.element(boundBy: ix) if image.exists { image.click() } } // why do I have to click this twice? Output says the second // click does "Falling back to element center point". app.buttons["Add"].firstMatch.click() app.buttons["Add"].firstMatch.click() Other than the minor annoyance of having to click the Add button twice that works fine. The issue is the second time in the same test I run almost identical code, but only try to select the first image as a test for handling duplicate selections. Doesn't work. The first image returned from the query exists, but is not hittable. This is a testing issue as running the steps manually work fine. The element I want to click is this: Attributes: Image, 0x73511d540, {{1794.0, 745.2}, {98.0, 73.5}}, identifier: 'PXGGridLayout-Info', label: 'February 02, 1:00 PM' Any ideas?

A lot of us seem to be having issues with Apple Developer Program enrollment. We paid, and then got stuck. I’ve been waiting 4 days without any response so far, which honestly seems mild compared to some others here. A lot of people are opening separate threads about this, and I’m sure many more are not posting at all. At some point these issues will probably get resolved, and it would be really helpful for others to know how long it actually took. So if your case was resolved, please leave a comment with how long it took and whether you did anything that helped move it forward. Common Patterns: Support is not responsive. Emails often go unanswered. My guess is they’re overwhelmed and heavily delayed. They may eventually get back to you, but don’t expect quick replies. Apple is not very active here either. I couldn’t find any reply from an Apple representative on this issue in the last two weeks. There used to be a phone number people could call, but apparently that is no longer the case. If you call regular Apple Support, they’ll usually tell you they can’t help and that there is no phone support for Developer Program. Enrolling through the website seems to take longer. From what people report, this is because Apple requires identity verification through the app, but for some reason does not make that clear on the website. “Second payment” - if your payment went through successfully, the Apple Developer site may still ask you to pay again. Don’t do it. You may end up paying twice. If you already received an invoice, do not make a second payment. If you already paid and got an invoice, don’t cancel your enrollment just to try again through the app. From what people report, that does not help. Some people report payment failures. If that happens, it may not be your fault. You can try a different payment method, but if it still fails, there’s a good chance the issue is on Apple’s side. Contact support. Some people wait for weeks without any response, so be prepared for that possibility.

My app uses SwiftData so I need at least iOS 17 as the minimum deployment target. When I select iOS 17 in the dropdown it selects iOS 17.6 as the target. However, the newest simulator available is iOS 17.5. Should I set my minimum deployment target to 17.0, 17.5, 17.6, or something else?

Hi, I’m enrolling in the Apple Developer Program as an individual. My subscription purchase was already confirmed by email, my card was charged, and I received Apple’s invoice 5 days ago. However, my developer membership is still not activated. When I sign in on the website, it still shows “Proceed with Purchase,” and now the Apple Developer support form fails every time with: “There was a problem processing your request.” Case ID: 102852545057 Enrollment ID: Y6WK6Q84XQ Sequence: 2-8744915202 Order ID: MKX7B85M1F Has anyone had the same issue? Thank you.

Hi, I’m enrolling in the Apple Developer Program as an individual from Albania. I completed the purchase through the Apple Developer app on iPhone. My credit card was charged, and I already received Apple’s invoice, but my account is still not activated after 5 days. In the app, I saw a message saying a confirmation email would be sent. On the website, when I log in with the same Apple Account, it still shows “Proceed with Purchase.” I already contacted Apple Developer Support and opened a case, but I have not received a response yet. Has anyone had the same issue after payment was already charged and invoiced? Thank you.