Hi everyone, I subscribed to the Apple Developer Program on Tuesday evening, November 4th, 2025. The payment has already been charged to my bank account, but my account still shows the status “Pending” with the message “Subscribe your membership”. It’s now been several days, and I haven’t received any confirmation email or any request for additional information. I already contacted Apple Support by email, but I’d like to know if other developers have experienced the same situation and how long it took before their account was activated. Thanks in advance for your help and feedback! — Martin

Hi, I’m facing a consistent simulator boot issue that appears to start after iOS 18.2 simulator runtimes and persists in 18.6, 26.1, and 26.2. Observed behavior iOS 18.2 simulator works fine iOS 18.6 simulator does NOT boot iOS 26.1 / 26.2 simulators do NOT boot Tried everything reinstall/clear cache and all and event formatted the system Unable to boot the Simulator NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding macOS: Sequoia Xcode: 26.1, 26.2 Machine: Apple Silicon Unable to boot the Simulator. Domain: NSPOSIXErrorDomain Code: 4 Failure Reason: Interrupted system call User Info: { DVTErrorCreationDateKey = "2025-12-26 02:19:27 +0000"; IDERunOperationFailingWorker = "_IDEInstalliP.honeSimulatorWorker", Session = "com apple CoreSimulator.SimDevice CCDECA56-4A59-491B-A830-0F3928FCD957"; } Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding Domain: com.apple.SimLaunchHostService.RequestError Code: 4 Event Metadata: com.apple. dt. DERunOperationWorkerFinished : { "device_identifier" = "CCDECAE6-4A59-491B-A830-0E3928FCD957"; "device_model" = "iPhone18, 1"; "device_osBuild" = "26.1 (23B86)"; "device_osBuild_monotonic" = 2301008600; "device_os_variant" = 1; "device_platform" = "com apple.platform.iohonesimulator"; "device_platform_family" = 2; "device_reality" = 2; "device_thinningType" = "iPhone18,1"; "device_transport" = 4; "launchSession_schemeCommand" = Run; "launchSession_schemeCommand_enum" = 1; "launchSession_targetArch" = arm64; "launchSession_targetArch_enum" = 6; "operation_duration_ms" = 1183; "operation_errorCode" = 4; "operation_errorDomain" = NSPOSIXErrorDomain; "operation_errorWorker" = "_IDEInstalliPhoneSimulatorWorker"; "operation_error_reportable" = 1; "operation_name" = IDERunOperationWorkerGroup; "param_consoleMode" = 1; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 1; "param_debugger_type" = 3; "param_destination_isProxy" = 0; "param_destination_platform" = "com apple platform Please help on this as it got stuck. Thanks

I am trying to upgrade my app to use Xcode 26 and I cannot get my tests to launch. I am trying to launch tests to the simulator, and I always get this error after 300 second timeout: "encountered an error (The test runner hung before establishing connection.)" There are no other errors getting logged. I can run to the same simulator just fine, and in Xcode 16 the tests launch with no issues. The tests also run fine on an actual iPhone. Thanks in advance.

Dear Apple Developer Support Team, I hope this message finds you well. I am writing to seek assistance regarding my Apple Developer account, which is still pending approval. It has been several days since I completed the registration process and submitted all the required information, but I have not received any confirmation or update yet. I understand that the review process can take some time, but as I urgently need access to my developer account for an ongoing project, I would greatly appreciate it if you could look into this matter and provide an update on the current status of my application Please let me know if any additional information or verification is required from my side to expedite the process. Thank you for your time and support. I look forward to your prompt response

Hi, It is the second time I am trying to create a Developer account and having the same issue. First time, my account was "pending" for weeks until the payment were refunded to my account. I called to Apple Store, which told me the issue could be with the bank processing. I called the bank, which said the issue could be with Apple processing. Now again, trying it, and Pending... Anyone had this issue and could give me some help please ?

Description I've encountered a consistent hang/freeze issue in SwiftUI applications when using nested LazyVStack containers with Accessibility Inspector (simulator) or VoiceOver (physical device) enabled. The application becomes completely unresponsive and must be force-quit. Importantly, this hang occurs in a minimal SwiftUI project with no third-party dependencies, suggesting this is a framework-level issue with the interaction between SwiftUI's lazy view lifecycle and the accessibility system. Reproduction Steps I've created a minimal reproduction project available here: https://github.com/pendo-io/SwiftUI_Hang_Reproduction To Reproduce: Create a SwiftUI view with the following nested LazyVStack structure: struct NestedLazyVStackView: View { @State private var outerSections: [Int] = [] @State private var innerRows: [Int: [Int]] = [:] var body: some View { ScrollView { LazyVStack(alignment: .leading, spacing: 24) { ForEach(outerSections, id: \.self) { section in VStack(alignment: .leading, spacing: 8) { Text("Section #\(section)") // Nested LazyVStack LazyVStack(alignment: .leading, spacing: 2) { ForEach(innerRows[section] ?? [], id: \.self) { row in Text("Section #\(section) - Row #\(row)") .onAppear { // Load more data when row appears loadMoreInner(section: section) } } } } .onAppear { // Load more sections when section appears loadMoreOuter() } } } } } } Enable Accessibility Inspector in iOS Simulator: Xcode → Open Developer Tool → Accessibility Inspector Select your running simulator Enable Inspection mode (eye icon) Navigate to the view and start scrolling Result: The application hangs and becomes unresponsive within a few seconds of scrolling Expected Behavior The application should remain responsive when Accessibility Inspector or VoiceOver is enabled, allowing users to scroll through nested lazy containers without freezing. Actual Behavior The application freezes/hangs completely CPU usage may spike The app must be force-quit to recover The hang occurs consistently and is reproducible Workaround 1: Replace inner LazyVStack with VStack LazyVStack { ForEach(...) { section in VStack { // ← Changed from LazyVStack ForEach(...) { row in ... } } } } Workaround 2: Embed in TabView TabView { NavigationStack { NestedLazyVStackView() // ← Same nested structure, but no hang } .tabItem { ... } } Interestingly, wrapping the entire navigation stack in a TabView prevents the hang entirely, even with the nested LazyVStack structure intact. Questions for Apple Is there a known issue with nested LazyVStack containers and accessibility traversal? Why does wrapping the view in a TabView prevent the hang? Are there recommended patterns for using nested lazy containers with accessibility support? Is this a timing issue, a deadlock, or an infinite loop in the accessibility system? Why that happens? Reproduction Project A complete, minimal reproduction project is available at: https://github.com/pendo-io/SwiftUI_Hang_Reproduction

Hi everyone, I registered for the Apple Developer Program about a week ago and my status is still Pending. I’ve emailed Apple but haven’t received any response yet. Just wondering if others are experiencing the same thing recently, or if there’s another way to follow up. Thanks a lot!

Hi, Some crashes downloaded from TestFlight aren't symbolicated by Xcode and I don't know why, here's an example: Although all uploaded builds contain debug symbols (Symbols directory with .symbols files) and other crashlogs in the same version are symbolicated just fine (also visible on the above SS). I have access only to the .symbols files but not to the original dSYMs and I wonder how to perform symbolication manually. I tried pointing atos and symbolicatecrash utilities to respective .symbols file, but they are unable to work with it. I'm sure it's possible as TestFlight symbolicates crashlogs using only .symbols files somehow. Could you give a hint?

Hi everyone, My Apple Developer account is still pending approval. Payment has been successfully charged from my bank, and all required steps are completed. Has anyone experienced this recently or knows the current approval timelines? I have my Order ID available if needed. Thanks.

I’m attempting to install the Metal toolchain in Xcode, but the installation keeps hanging. Through Xcode, it stops at the “Processing” step, and via the terminal, it never goes past “Beginning asset download…”.

While debugging a Swift application in Xcode, LLDB crashes with an assertion failure related to LLDBMemoryReader and pointer authentication. The issue occurs during normal debugging (e.g. inspecting variables or stack frames), and causes the debugger to become unusable. The error appears to be triggered inside the Swift language runtime reflection path in LLDB error: Assertion failed: (LLDBMemoryReader module to address map ran into pointer authentication mask!), function addModuleToAddressMap, file /AppleInternal/Library/BuildRoots/603ae698-b099-11ef-b64c-aabfac210453/Library/Caches/com.apple.xbs/Sources/lldb/llvm-project/lldb/source/Plugins/LanguageRuntime/Swift/LLDBMemoryReader.cpp, line 537 Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it): 0 LLDB 0x00000001240eb8f8 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 40 1 LLDB 0x0000000123bbd0a8 lldb_private::lldb_assert(bool, char const*, char const*, char const*, unsigned int) + 184 2 LLDB 0x0000000123d5379d lldb_private::LLDBMemoryReader::addModuleToAddressMap(std::__1::shared_ptr<lldb_private::Module>, bool) + 477 3 LLDB 0x0000000123dbb733 lldb_private::SwiftLanguageRuntimeImpl::AddObjectFileToReflectionContext(std::__1::shared_ptr<lldb_private::Module>, llvm::SmallVector<llvm::StringRef, 1u>) + 1043 4 LLDB 0x0000000123dbc6de lldb_private::SwiftLanguageRuntimeImpl::AddModuleToReflectionContext(std::__1::shared_ptr<lldb_private::Module> const&) + 2766 5 LLDB 0x0000000123dc6d60 std::__1::__function::__func<lldb_private::SwiftLanguageRuntimeImpl::ProcessModulesToAdd()::$_0, std::__1::allocator<lldb_private::SwiftLanguageRuntimeImpl::ProcessModulesToAdd()::$_0>, bool (std::__1::shared_ptr<lldb_private::Module> const&)>::operator()(std::__1::shared_ptr<lldb_private::Module> const&) + 32 6 LLDB 0x00000001239bdad2 lldb_private::ModuleList::ForEach(std::__1::function<bool (std::__1::shared_ptr<lldb_private::Module> const&)> const&) const + 66 7 LLDB 0x0000000123dba72a lldb_private::SwiftLanguageRuntimeImpl::ProcessModulesToAdd() + 346 8 LLDB 0x0000000123dba0c9 lldb_private::SwiftLanguageRuntimeImpl::GetReflectionContext() + 57 9 LLDB 0x0000000123dd32e9 lldb_private::SwiftLanguageRuntimeImpl::BindGenericTypeParameters(lldb_private::StackFrame&, lldb_private::TypeSystemSwiftTypeRef&, lldb_private::ConstString) + 121 10 LLDB 0x0000000123dd3b8b lldb_private::SwiftLanguageRuntimeImpl::BindGenericTypeParameters(lldb_private::StackFrame&, lldb_private::CompilerType) + 347 11 LLDB 0x0000000123dc980d lldb_private::SwiftLanguageRuntimeImpl::GetSwiftRuntimeTypeInfo(lldb_private::CompilerType, lldb_private::ExecutionContextScope*, swift::reflection::TypeRef const**) + 621 12 LLDB 0x0000000123dcf9b1 lldb_private::SwiftLanguageRuntimeImpl::GetBitSize(lldb_private::CompilerType, lldb_private::ExecutionContextScope*) + 49 13 LLDB 0x0000000123dc332f lldb_private::SwiftLanguageRuntime::GetBitSize(lldb_private::CompilerType, lldb_private::ExecutionContextScope*) + 63 14 LLDB 0x0000000123fb0dd1 lldb_private::TypeSystemSwiftTypeRef::GetBitSize(void*, lldb_private::ExecutionContextScope*)::$_0::operator()() const + 689 15 LLDB 0x0000000123fb0aa8 lldb_private::TypeSystemSwiftTypeRef::GetBitSize(void*, lldb_private::ExecutionContextScope*) + 440 16 LLDB 0x0000000123aa9d61 lldb_private::CompilerType::GetBitSize(lldb_private::ExecutionContextScope*) const + 241 17 LLDB 0x0000000123aa9dc9 lldb_private::CompilerType::GetByteSize(lldb_private::ExecutionContextScope*) const + 9 18 LLDB 0x00000001239ef9e1 lldb_private::ValueObjectVariable::UpdateValue() + 241 19 LLDB 0x00000001239d9993 lldb_private::ValueObject::UpdateValueIfNeeded(bool) + 1011 20 LLDB 0x00000001239dac20 lldb_private::ValueObject::GetError() + 16 21 LLDB 0x0000000123868231 ValueImpl::GetSP(lldb_private::ProcessRunLock::ProcessRunLocker&, std::__1::unique_lock<std::__1::recursive_mutex>&, lldb_private::Status&) + 145 22 LLDB 0x000000012385cd28 lldb::SBValue::GetSP(ValueLocker&) const + 376 23 LLDB 0x000000012385dab9 lldb::SBValue::GetValueType() + 297 24 lldb-rpc-server 0x000000010f2f730a rpc_server::_ZN4lldb7SBValue12GetValueTypeEv::HandleRPCCall(rpc_common::Connection&, rpc_common::RPCStream&, rpc_common::RPCStream&) + 42 25 lldb-rpc-server 0x000000010f300749 rpc_common::Connection::PrivateHandleRPCPacket(rpc_common::RPCPacket&, rpc_common::RPCPacket&, bool&) + 1337 26 lldb-rpc-server 0x000000010f304434 Packets::ProcessPackets() + 564 27 lldb-rpc-server 0x000000010f30418a Packets::ReadThread() + 314 28 lldb-rpc-server 0x000000010f304049 Packets::RunReadThread(void*) + 9 29 libsystem_pthread.dylib 0x00007ff81847018b _pthread_start + 99 30 libsystem_pthread.dylib 0x00007ff81846bae3 thread_start + 15 Please file a bug report against lldb reporting this failure log, and as many details as possibleerror: Assertion failed: (LLDBMemoryReader module to address map ran into pointer authentication mask!), function addModuleToAddressMap, file /AppleInternal/Library/BuildRoots/603ae698-b099-11ef-b64c-aabfac210453/Library/Caches/com.apple.xbs/Sources/lldb/llvm-project/lldb/source/Plugins/LanguageRuntime/Swift/LLDBMemoryReader.cpp, line 537

I have a Xcode project with two apps that have a separate MainMenu.nib file. Both are different apps with different source trees.. Why am I seeing resources in interface builder from one app in another? I am a bit old school and using the AppDelegate rather than view controllers to capture events... but that should work fine Thanks ahead of time.

My workflow is using Xcode 16.4 and macOS Tahoe 26.2 (25C56). I am trying to change Xcode version to 26.2. When I click Save after some time I get "Something went wrong" error message without any additional details (see screenshot). I get the same error for the following cases: Tried changing a different workflow Tried to deactivate a workflow Tried various combinations of Xcode (26.1, 26.1.1, 26.2) + mac OS (26.1, 26.2) Tried creating a new workflow with Xcode 26.2 (haven't tried any other Xcode versions though)

Whats the deal with apple taking money from people for a developer account and doing nothing about it. There's a growing number of users waiting weeks and some over a month who have paid for a developer account and are not receiving what they paid for. When trying to reach out to Apple they are ignored and never answered. Some would label this theft or fraud. Whats going on?

Hey folks, Looking for some assistance with using an API key with xcodebuild commands to archive/export builds on our Enterprise developer account. The goal here is to allow Xcode to completely manage signing/certificates with our cloud distribution certificate, since these builds are happening in CI and we don't want to be manually handling user sessions/certificates on these machines. This is working great with our App Store account, but with our Enterprise account we're getting errors both archiving and exporting the builds. Here's an example of an export command that is giving errors: xcodebuild -exportArchive -exportOptionsPlist /path/to/exportOptions.plist -archivePath /path/to/archive.xcarchive -exportPath /path/to/export -authenticationKeyID *** -authenticationKeyIssuerID *** -authenticationKeyPath /path/to/key.p8 -allowProvisioningUpdates I've put some example values there, but we've double/triple checked the real values when this is actually running. These are the errors we're getting: 2026-02-02 12:30:04.022 xcodebuild[59722:1854348] DVTServices: Received response for 0794248F-E534-474D-ABBF-40C1375B6590 @ <https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA>. Error = Error Domain=DVTPortalResponseErrorDomain Code=0 "Communication with Apple failed" UserInfo={NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (401) for URL https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA} 2026-02-02 12:30:04.173 xcodebuild[59722:1854348] DVTServices: Received response for 1D51FCD1-1876-4881-BE89-DD44E78EA776 @ <https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA>. Error = Error Domain=DVTPortalResponseErrorDomain Code=0 "Communication with Apple failed" UserInfo={NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (401) for URL https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA} 2026-02-02 12:30:04.322 xcodebuild[59722:1854344] DVTServices: Received response for 25D7983F-1153-47C9-AE8A-03A8D10B6453 @ <https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA>. Error = Error Domain=DVTPortalResponseErrorDomain Code=0 "Communication with Apple failed" UserInfo={NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (401) for URL https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA} 2026-02-02 12:30:04.483 xcodebuild[59722:1854344] DVTServices: Received response for 8A56C98B-E786-4878-856F-4D7E3D381DEA @ <https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA>. Error = Error Domain=DVTPortalResponseErrorDomain Code=0 "Communication with Apple failed" UserInfo={NSLocalizedDescription=Communication with Apple failed, NSLocalizedRecoverySuggestion=A non-HTTP 200 response was received (401) for URL https://appstoreconnect.apple.com/xcbuild/QH65B2/listTeams.action?clientId=XABBG36SBA} error: exportArchive Communication with Apple failed error: exportArchive No signing certificate "iOS Distribution" found We get very similar errors when archiving as well. Are we doing something incorrect here? Is API key usage with xcodebuild not supported for Enterprise builds? Appreciate any help y'all can provide!

We are currently developing a research-based iOS application that relies heavily on background capabilities, specifically Significant Location Change. We are using CLLocationManager.startMonitoringSignificantLocationChanges(). During development, when using Debug → Simulate Location in Xcode, we receive a location update only once. Subsequent simulated location changes do not trigger additional callbacks, which makes testing and development quite cumbersome. Are there any tools, commands, or workflows (e.g., via Xcode, Instruments, or system-level simulation) to reliably simulate multiple significant location change callbacks for testing purposes? If there aren't such tools, how do I test this behaviour reliably, robustly and rigidly?

Hello i tried to enroll for Apple developer program but i got that messageYour enrollment could not be completed."Your enrollment in the Apple Developer Program could not be completed at this time."And i am not able to proceed further.Thanks

If you add a new string in your app (for example String(localized: "contact_support_message", defaultValue: "Please contact support")), then later you change that default value and rebuild, the string catalog updates to match as expected. But once that string is translated, changing the default value in code and rebuilding does not update the catalog. You seemingly have to go manually change the default value for English in the catalog to match the code (which marks the translation as Needs Review). Is there a better way? Or is there a way to determine what strings have default values in code that do not match the catalog values to see if any were missed as wording was tweaked over time?

Hello, I am trying out Xcode Cloud for the first time. I could connect to Github in the initial setup and had a few failed builds (package resolution error), which I resolved fairly quickly. Now whenever I am trying to build, I get the following error: Xcode Cloud is unable to connect to the repository “<respository-name>”. Reconnect the repository to resume builds. I am unable to remove the connection from settings as well because it's stuck in a loading state. Is there a way to fix this?

Dear Apple Developer Program Legal/Compliance Team, I am writing in response to the termination notice regarding my Apple Developer Program account, in which Apple cites an alleged violation of Section 3.2(f) of the Apple Developer Program License Agreement (ADP Agreement), based on “documented indications of fraudulent conduct.” I respectfully request formal clarification and detailed information regarding this determination, as I take compliance obligations under Apple’s agreements very seriously. Specifically, I kindly request the following: Clarification of Alleged Conduct Please specify the exact actions, behaviors, or activities that Apple has determined to constitute a violation of Section 3.2(f), including the category of conduct involved (e.g., technical interference, platform misuse, fraudulent activity, distribution abuse, business practice violations, or other). Scope and Nature of the Evidence Without requesting disclosure of sensitive internal systems, I respectfully ask for clarification regarding the general nature of the evidence relied upon (e.g., transactional records, system logs, behavioral patterns, policy violations, or platform integrity signals). Account-Level vs. Application-Level Issues Please confirm whether the alleged violation relates to: A specific application or applications, Account-level activity, Distribution mechanisms (TestFlight, Custom App Distribution, Ad Hoc, etc.), Or external operational behavior associated with the developer account. Opportunity for Rectification or Compliance Remediation Kindly advise whether Apple provides any compliance remediation pathway, corrective action mechanism, or review process for cases involving Section 3.2(f), including: Formal reconsideration or appeal procedures, Regulatory complaint mechanisms, Compliance audit or corrective action submissions, Reinstatement eligibility criteria. Reapplication and Cooling-Off Period Requirements Please clarify the conditions, requirements, and compliance expectations associated with the stated reapplication restriction period, including whether specific remediation steps, certifications, or compliance documentation may be required prior to any future eligibility review. My intent is to fully understand the nature of the determination, ensure full legal and contractual compliance, and clarify whether any formal resolution or review mechanisms exist under Apple’s policies or applicable platform regulations. I respectfully request that this inquiry be handled through the appropriate legal or compliance review channel. Thank you for your time and consideration. Sincerely, Jiuru Song [Team ID / Developer ID if available]8DJDU79WZ7 [Company Name, if applicable]ASIA DIGITAL ALLIANCE PTE. LTD.