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!

I have purchased membership for personal use to see how publishing app works. The cost was taken from the credit card I had given. but when i check my account its still reflecting the same "Purchase your membership" and ask me to purchase again

I'm struggling to build a driver for iPadOS in a particular project configuration. If I put the driver code and dext target into the same Xcode project which contains the iPad app, all is well. This is the way the Xcode driver template does it. However, I'd like to build and debug the dext on macOS, while eventually deploying on iPadOS. So I put the dext into a different project, which has a macOS target, a minimal iPadOS target and a DriverKit target. I made a workspace which contains both projects. I dragged the macOS project into the iPadOS project so that I can refer to the products of the macOS project (specifically, its driver target) as a dependency of the iPadOS target. Note that the main iPad app target depends on the driver target. So the workspace organization looks like this: Workspace iPad project main iPad app target (depends on driver) test project reference test project test macOS/iPad app target DriverKit dext target When I build the iPadOS target, it builds the dependent driver target in the macOS project, but it fails to link because Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/15.0.0/lib/darwin/libclang_rt.profile_driverkit.a is not found. If I just build the driver target directly in Xcode, there is no such complaint. I looked closely at the build logs, and I see for the failed link, there are these two linker flags set which are not set in the successful case -debug_variant -fprofile-instr-generate I can't seem to control the generation of this flag. I tried turning off the Profile switch in the Scheme editor for the driver, but is makes no difference. When I directly build the driver target, no -fprofile-instr-generate is set and it compiles and links. When i build the driver as a dependency of another target, -fprofile-instr-generate is passed to the linker, which fails. The obvious workaround is to put the driver source code into a separate driver target in the iPadOS project, but I'd rather have just one DriverKit driver for both platforms, with a few settings (such as bundle ID) controlled by a configuration file. Has anyone else encountered this problem, and know of a workaround?

I use spm manage swift package, now i want my macos app support arm64e,so i add arm64e in Build Srtting -> Architectures. but i got error Could not find module 'SwiftyJSON' for target 'arm64e-apple-macos'; found: arm64-apple-macos, x86_64-apple-macos Apparently, if no limit in Package.swift, SPM will only compile versions for x86 and ARM64 architectures by default. now, how should I configure SPM to compile the arm64e version? thanks

hi, the email i used to create my apple store is no longer accessible by me... I need to change it, but have no way of contacting since when I click "contact for an issue" it defautls to that email that I can't see

Hello, I am having a recurring issue using Swift Playgrounds version 4.6.4 on macOS 26.1. Upon opening a file and every other time I start typing in the code section I get a prompt, the image below, two or three times. It doesn't matter if I accept or decline all or some of the prompts, as soon as I start typing on another line I get prompted another two or three times for permission. It appears to me that prompt generates every time the preview pane tries to update. Declining the prompt breaks the preview but accepting the prompt only gets you through a single line of code before it appears again. I believe this issue started after I updated to macOS26.1 as I had not encountered it before. I've also opened other files with Swift Playgrounds and encounter the same problem. It could also be unrelated to the update and could be an issue with some permission setting somewhere, however, I have been unable to find what or where it could be. Is anyone else experiencing this? Thank you for your time :)

Dear Apple Developer Support Team, I am writing to request assistance regarding an issue I am experiencing while attempting to enroll in the Apple Developer Program. Below are the details of the problem: The enrollment process fails before reaching the payment page. The message displayed is: “Your enrollment could not be completed.” The error appears prior to any payment attempt. Two-factor authentication is enabled on the Apple ID. Email address and phone number are verified. The Apple ID being used for enrollment is different from our existing Enterprise account. We have attempted enrollment using: A U.S. address A Indian phone number A clean browser session (logged out of other Apple accounts) The existing Apple Enterprise account under our organization is active and functioning without issues. This new enrollment attempt is for a separate Developer Program account using a different email address. We have tried multiple browsers and networks, but the issue persists and prevents us from proceeding to payment. Could you please check whether: The Apple ID is restricted or flagged in your system? There are any verification issues preventing enrollment? Any additional steps are required from our side to complete registration? Kindly let us know how we can resolve this and proceed with successful enrollment. Thank you for your assistance.

Hello Apple Developer Support Team, I recently completed my Apple Developer Program enrollment through the website, and both the identity verification and payment steps were successfully completed. However, when I log in to my account, the website still displays the message “Complete Your Purchase,” and my enrollment status remains listed as Pending. It appears as though the system is prompting me to start the enrollment process again. Could you please review my account and confirm the current status of my enrollment? Thank you for your time and assistance. Kind regards,

Hi I'm new here and trying so enroll in apple developers program and so I was met with problems like unable to create apple account, failed payment on 7 cards, 3 support tickets with no responds, and now I have enrolled in apple developers program (sort of, they just took payment and no news after that. Now running 3 days since payment. Is this some sort of a hazing ceremony or a sick joke apple is doing to new developers? or is there a secret email I can contact to get some decent support?

Hi Apple Developer Support Team, I need urgent assistance with my Apple Developer Program enrollment. My details: Enrollment ID: AJ78LF239A Support Case: 102840241902 (opened 4 days ago, no response yet) Issue: I have completed all enrollment steps and entered my payment information correctly. When I click the "Continue" button to finalize the payment, the page freezes completely — no error message, no confirmation, nothing happens. Steps already taken: Confirmed with my bank that the card supports international purchases Removed and re-added the card in Apple ID settings Tried multiple times on different days and browsers Sent email to Apple Developer support (devprograms) Opened support case 102840241902 with no response This is blocking my app from being published on the App Store. I kindly request that someone manually process the payment or provide an alternative method to complete enrollment. Thank you.

Hello guys. I made a payment for developer program. 100 dollars taken, Apple dropped a letter about the invoice number, the order, everything seems to be fine. But website cannot find this order. Also my account in Apple Dev doesn’t see any purchase and asks to pay again. What i have to do in this situation?

Hello Developers, I need your help. I'm trying to pay for my Apple Developer Account, but it's being declined saying 'Your Purchase Could Not Be Completed'. I need to know where the problem is so I can successfully make the payment.

Please help! I can’t update my developer info and when I renew my membership I’m taken to an account that I had in Europe which I no longer use or have money tied to. I want to switch my account to USA and use a usa account

I have been trying to get into my account for several days now and I have tried everything. First of you cannot get support because you need to be logged in so had to make another account to be able to post this. And even then the support is not working. Send an email a while ago and tried the call option and I have gotten no response from both. I was supposed to launch my app last week and I have just not be able to log into my account. I keep getting the 'Too many verification codes have been sent. Enter the last code you received or try again later.' I didn't even do that, I just tried to log in and had that there. I have waited days and it's still there. I have tried changing the number for which I waited a day and now it's told me to wait another 6 days. This has caused so many problem and the lack of support is unbelievable. Can anyone please help me get into my account or advise on what I can do ASAP. Thanks, Usama

Hi I'm new here and trying so enroll in apple developers program and so I was met with problems like unable to create apple account, failed payment on 7 cards, 3 support tickets with no responds, and now I have enrolled in apple developers program (sort of, they just took payment and no news after that now running 3 days since payment. Is this some sort of a hazing ceremony or a sick joke apple is doing do new developers? or is there a secret email I can contact to get some decent support?

I’m creating a new post because the situation has gone far beyond reasonable. My Apple Developer Program enrollment has been stuck in “Pending” status for almost a month. During this time, I have sent around 10 emails to Apple Developer Program Support. Result: ZERO REPLISES. NO EXPLANATIONS NO UPDATES. NO HELP. If you are experiencing the same issue — or have faced it before — please leave a comment or upvote this thread so it gets visibility. At this point, this seems to be the only way to get Apple’s attention. Apple, this situation needs to be addressed.

Popular automated testing systems like FireBase [1] and WeTest [2] expect the uploaded test to include the Debug-iphoneos directory generated by Xcode. However, in all of our builds on Xcode 26.3, this folder is created but remains empty. There are some other folders with the same name in subdirectories, but these only contain intermediate build files. Now we're looking for configuration or settings in Xcode to restore the original behavior, where the top-level Debug-iphoneos directory gets populated with a complete image of the test target, include the binary and resource files. Any suggestions would be much appreciated! [1] https://firebase.google.com/docs/test-lab/ios/run-xctest [2] https://www.wetest.net/documents/detail/automation/d8yaA7yz

On XCode 26.x, calling XCFail with continueAfterFailure set to false causes xcodebuild command to hang indefinitely if the XCUIApplication object is stored outside the test method. Create a new template iOS App project with UI tests Add XCFail(...) to a UI test test-case Set the XCUIApplication in self.app (avoiding this fixes the hang) Run tests with xcodebuild test The terminal hangs forever Reproduction example import XCTest final class TestAppUITests: XCTestCase { var app: XCUIApplication? = nil override func setUpWithError() throws { continueAfterFailure = false } override func tearDownWithError() throws { app?.terminate() } @MainActor func testExample() throws { let app = XCUIApplication() self.app = app // <- HERE this causes the problem app.launch() XCTFail() } } Reproduction environment macOS Sequoia 15.7.3 Tested XCode 26.3 and XCode 26.2 have the hang Tested XCode 16.4 does work as expected XCode 16.4 The issue does not happen on XCode 16.4, and is likely introduced in XCode 26. Related threads: https://developer.apple.com/forums/thread/809989 https://developer.apple.com/forums/thread/793307 Work-around Do not store XCUIApplication in the XCTestCase instance, maintain it scoped to the test methods.

Thank you very much for choosing me to go to Apple Park to participate in WWDC. I am looking forward to participating in this event. May I ask you some questions? I am a young Apple Developer Program from China. And I am the winner of the Swift Student Challenge in 2024. I am over 13 years old. I used my own Developer account, not my parents', to apply for WWDC activities and all the events I carry out. Since I am under 18 years old, my parents may need to sign the Special Event Parental Permission Statement. Where can I find it? My parents will sign it. At the same time, I noticed that the bottom of the RSVP form requires me to guarantee that I am at least 18 years old, but I am not. And I used my own account to apply for WWDC, so I want to know how to meet this need? I need a non-immigrant visa to go to the United States. So, I need to prove to the visa officer that I have received an invitation from Apple. Could Apple send me a formal invitation letter to prove that I have received an invitation from Apple? At the same time, as a teenager, I need to go to the United States with my mother, so can you mention the information of my guardian (my mother) in the invitation letter? Ps: I am very independent. I am well aware that the number of people in WWDC is limited. My mother will not enter the venue unless otherwise required.

While Apple prides itself on providing the ultimate experience for both users and developers, many find themselves trapped in a technical "black hole" with no exit. The issue isn't just the complexity of the systems, but the sheer inability of these systems to handle a developer’s most basic need: accessing their account to manage their business. The Dead-End Loop: "Too Many Verification Codes" The disaster begins with a seemingly harmless but business-destroying message: "You have sent too many verification codes. Please try again later." At this point, Apple’s system—with its supposed "intelligence"—decides to freeze your account for two days or more. You wait patiently, return after 48 hours to log in, only to be met by the exact same message. This isn’t "security"; it’s primitive technical failure. How can a company of Apple’s magnitude fail to program a smart system that distinguishes between a breach attempt and a developer trying to access their work tools? Persistent failure for over a month without a root solution raises serious questions about the software infrastructure of this giant. Customer Support: Total Absence and Disregard for Time The greatest agony lies in the "Non-Response." You email technical support, and the answer either arrives a month later—long after the damage is done—or never arrives at all. In the business world, every second translates to money and reputation, but in Apple’s dictionary, it seems a developer’s time has no value. It is ironic that a trillion-dollar company fails to provide a human support agent who can, with a single click, verify a developer's identity and bypass a stuck OTP. This blatant lack of effective human support is the pinnacle of negligence toward the developer community—the very backbone of their App Store. Paralyzed Apps and Users Left Stranded Behind this "technical incompetence" lies a painful reality: an app with technical bugs requiring urgent fixes, thousands of users waiting for an update that never comes, and business operations completely halted. The developer stands handcuffed, unable to push a single update because the "fortress gates" are locked due to a glitch in sending a text message! How has Apple managed to reach this size while operating with such technical bureaucracy? The answer may lie in its market monopoly, which has made it indifferent to the collateral damage inflicted on startups by its software errors and the absence of its support staff. Final Word What is happening is not just a passing technical glitch; it is an "administrative catastrophe" wrapped in technology. Apple must realize that its continued success depends not just on selling devices, but on respecting the minds and time of the developers who build its ecosystem. We aren’t asking for miracles; we are simply asking for a login system that works and human beings who respond to emails before it’s too late.