I work on some proprietary codebases and can only use private AI services with them (currently MiniMax M2.1 and GLM 4.7). It all works great with both Claude Code and OpenCode agents, and I'd like to leverage the new agentic capabilities that are now in Xcode 26.3. I'm not seeing any option to connect to OpenCode, and both the Anthropic and OpenAI providers require an enterprise account (which I don't have access to). Are there any options that I'm missing here?

Hey all, I recently updated to Xcode 26.2 and I'm having the hardest time trying to download the corresponding iOS simulator. I installed Xcode from developer downloads and the app did not come loaded with an iOS simulator. When trying to download from Components in Settings, I only get the following message: Download failed due to a bad URL. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime) Domain: com.apple.MobileAssetError.Download Code: 49 User Info: { checkConfiguration = 1; } I also tried downloading via Terminal but also get a download failed message. I am on the latest macOS and have over 600 GB of disk space available. In previous versions, I was able to download the iOS simulator directly from Developer Downloads, but anything after 26 is not there. Any suggestions?

When I use Xcode 26 (0.1, 1) for debugging and hit a breakpoint, using "step over" causes the debugger to freeze at a random line of code. Clicking "Pause program execution" indicates that the line is being executed, but the breakpoint never exits, seemingly causing a freeze. The application on the simulator also becomes unresponsive. However, when I do not use breakpoints, my program runs smoothly, and debugging on a physical device does not cause any freezes. This issue only occurs with the simulator. I am using Xcode on Apple Silicon, and due to some third-party SDKs that depend on Rosetta, our app can only run on the Rosetta simulator. We did not encounter this issue when using Xcode 16.x for simulator debugging. The current situation with Xcode 26.x significantly reduces our development efficiency. What could be causing this, and is there a solution?

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?

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

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?

I have purchased the apple developer account about 2 months ago, my account has not been activated since then. I have reached apple support multiple times over mails, but received no response. We have also shared our D-U-N-S number multiple times over email. Case ID: 102773282429

Hi everyone, I subscribed to the Apple Developer Program on Tuesday evening, Jan 30th, 2025. The payment has already been successfully charged to my bank account, but my account is still showing “Pending” with the message “Subscribe your membership.” It has been several days now, and I haven’t received any confirmation email or any request for additional verification. I’ve already contacted Apple Developer Support via email, but I wanted to check here as well. Has anyone else faced this issue recently? How long did it take for your membership to become active? Any insights or experiences would be greatly appreciated. Thanks in advance!

I've suddenly started seeing hundreds of the same block of four error messages (see attached image) when running my app on my iOS device through Xcode. I've tried Cleaning the Build folder, but I keep seeing these messages in the console but can't find anything about them. Phone is running iOS 26.1. Xcode is at 16.4. Mac is on Sequoia 15.5. The app is primarily a MapKit SwiftUI based application. Messages below: Connection error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.PerfPowerTelemetryClientRegistrationService was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} (+[PPSClientDonation isRegisteredSubsystem:category:]) Permission denied: Maps / SpringfieldUsage (+[PPSClientDonation sendEventWithIdentifier:payload:]) Invalid inputs: payload={ isSPR = 0; } CAMetalLayer ignoring invalid setDrawableSize width=0.000000 height=0.000000 I'm also seeing the following error messages: CoreUI: CUIThemeStore: No theme registered with id=0

{ "logFormatVersion": 1, "jobId": "e2ec4d13-bb83-41d4-a497-ba80cf830af1", "status": "Rejected", "statusSummary": "Team is not yet configured for notarization. Please contact Developer Programs Support at developer.apple.com under the topic Development and Technical / Other Development or Technical Questions.", "statusCode": 7000, "archiveFilename": "Lens.zip", "uploadDate": "2026-01-23T16:13:37.589Z", "sha256": "fd52815d5edf14b66b25529e89c207b2acff2c41642261e1049a479f19f2b72f", "ticketContents": null, "issues": null }} I am getting this error and have opened a support ticket for 3months so far and neither the development team or engineering team has replied as to why our development account has been BLOCKED. We just signed up, and are a legal entity in delaware. To other developers, how have you proceeded with such issues?

Hi everyone 👋 As a network engineer and indie iOS developer, I couldn’t find a lightweight mobile tool that fully supports IPv4/IPv6 dual-stack diagnostics — so I built NetToolbox -All-In-One Utility for engineers, DevOps, and developers. Here are its core features that solve real mobile networking pain points: One-Click Full Diagnostics: Integrates ping, traceroute, and multi-type DNS queries (A/AAAA/CNAME) — no need to switch between apps IPv4/IPv6 Dual-Stack Support: Seamlessly works in IPv6-only networks, with the ability to test connectivity differences between dual-stack environments LAN Device Scanning: Quickly identifies all devices on the same network segment and checks port availability Offline Functionality: Diagnostic logic is stored locally, enabling LAN troubleshooting without an internet connection Lightweight Design: 5MB install size, no storage bloat, and low power consumption during operation Dark Mode Support: Tailored for developers who work late at night During development, I leveraged Apple Intelligence alongside Claude Code and Gemini 3 to accelerate the process, optimize iOS native networking stack adaptation and local storage logic, and significantly boost development efficiency. I’d love to hear from the community: What must-have features are missing from mobile network diagnostic tools? Do you have experience optimizing iOS workflows with Apple Intelligence? 👉 You can try the app here: https://apps.apple.com/us/app/nettoolbox-all-in-one-utility/id6757392404 Feedback is highly appreciated — I’ll keep iterating to make it better! 🚀

I can't find the full content of the SwiftUI inspector in the latest version of Xcode. I've opened the preview canvas but it still won't display.

Need help with Apple Developer Program enrollment. What happened: Paid $99 on Jan 14 from Pakistan (HabibMetro bank) Money fully deducted from my account Apple says "payment problem" and gives me 7 days or enrollment cancels Bank needs 10 days to trace the payment The problem: -Apple will cancel before bank finishes tracing (7 days vs 10 days). -Apple Support suggested re-enrolling with their app using different payment method, but I'm worried about: Getting charged twice First payment not refunded Losing the $99 Questions: Anyone faced this? What did you do? Should I re-enroll or wait? How to avoid double payment? Order: D004702861 Case: 102802965662 Any advice appreciated

In our app, we implement a document picker using FilePickerManager+available.m, selecting different APIs based on the iOS version: if (@available(iOS 14.0, *)) { NSMutableArray<UTType *> *contentTypes = [NSMutableArray array]; for (NSString *uti in documentTypes) { UTType *type = [UTType typeWithIdentifier:uti]; if (type) { [contentTypes addObject:type]; NSLog(@"iOS 14+ Adding type: %@", uti); } else { NSLog(@"Warning: Unable to create UTI: %@", uti); } } UIDocumentPickerViewController *documentPicker = [[UIDocumentPickerViewController alloc] initForOpeningContentTypes:contentTypes]; documentPicker.delegate = self; documentPicker.allowsMultipleSelection = NO; [self.presentingViewController presentViewController:documentPicker animated:YES completion:nil]; } However, we've observed inconsistent symbol reference types to UTType in the final linked binaries: One build results in a strong reference to UTType. Another demo project (with seemingly identical code and build settings) results in a weak reference. Both object files (.o) show undefined references to UTType symbols (e.g., UTTypeCreatePreferredIdentifierForTag), yet the final linked binaries differ in how these symbols are resolved. Impact of the Issue This inconsistency causes problems on iOS 14.0+ devices: Strong reference version: Fails to launch on devices where the UniformTypeIdentifiers framework is not present (e.g., certain older iOS 14.x devices), due to link-time failure. Weak reference version: Launches successfully but crashes at runtime when attempting to call UTType methods, because the implementation cannot be found. Our Analysis Using nm -u, both versions show an undefined symbol: U _UTTypeCreatePreferredIdentifierForTag However, in the final binaries: One shows: T _UTTypeCreatePreferredIdentifierForTag (strong) The other shows: W _UTTypeCreatePreferredIdentifierForTag (weak) Both projects link against the framework identically in their build logs: -framework UniformTypeIdentifiers (no -weak_framework flag is used in either case). Questions Why do identical source code and linker flags result in different symbol reference strengths (T vs W) for the same framework? Are there specific compiler or linker behaviors (e.g., deployment target, SDK version, module imports, or bitcode settings) that influence whether symbols from UniformTypeIdentifiers are treated as strong or weak? What is the recommended best practice to ensure consistent symbol referencing when using newer APIs like UTType, especially when supporting older OS versions? We aim to understand this behavior to guarantee stable operation across all supported iOS versions—avoiding both launch failures and runtime crashes caused by inconsistent symbol linking. Any insights or guidance from the community or Apple engineers would be greatly appreciated! Let me know if you'd like a shorter version or want to include additional build environment details (Xcode version, deployment target, etc.)!

In our app, we implement a document picker using FilePickerManager+available.m, selecting different APIs based on the iOS version: if (@available(iOS 14.0, *)) { NSMutableArray<UTType *> *contentTypes = [NSMutableArray array]; for (NSString *uti in documentTypes) { UTType *type = [UTType typeWithIdentifier:uti]; if (type) { [contentTypes addObject:type]; NSLog(@"iOS 14+ Adding type: %@", uti); } else { NSLog(@"Warning: Unable to create UTI: %@", uti); } } UIDocumentPickerViewController *documentPicker = [[UIDocumentPickerViewController alloc] initForOpeningContentTypes:contentTypes]; documentPicker.delegate = self; documentPicker.allowsMultipleSelection = NO; [self.presentingViewController presentViewController:documentPicker animated:YES completion:nil]; } However, we've observed inconsistent symbol reference types to UTType in the final linked binaries: One build results in a strong reference to UTType. Another demo project (with seemingly identical code and build settings) results in a weak reference. Both object files (.o) show undefined references to UTType symbols (e.g., UTTypeCreatePreferredIdentifierForTag), yet the final linked binaries differ in how these symbols are resolved. Impact of the Issue This inconsistency causes problems on iOS 14.0+ devices: Strong reference version: Fails to launch on devices where the UniformTypeIdentifiers framework is not present (e.g., certain older iOS 14.x devices), due to link-time failure. Weak reference version: Launches successfully but crashes at runtime when attempting to call UTType methods, because the implementation cannot be found. Our Analysis Using nm -u, both versions show an undefined symbol: U _UTTypeCreatePreferredIdentifierForTag However, in the final binaries: One shows: T _UTTypeCreatePreferredIdentifierForTag (strong) The other shows: W _UTTypeCreatePreferredIdentifierForTag (weak) Both projects link against the framework identically in their build logs: -framework UniformTypeIdentifiers (no -weak_framework flag is used in either case). Questions Why do identical source code and linker flags result in different symbol reference strengths (T vs W) for the same framework? Are there specific compiler or linker behaviors (e.g., deployment target, SDK version, module imports, or bitcode settings) that influence whether symbols from UniformTypeIdentifiers are treated as strong or weak? What is the recommended best practice to ensure consistent symbol referencing when using newer APIs like UTType, especially when supporting older OS versions? We aim to understand this behavior to guarantee stable operation across all supported iOS versions—avoiding both launch failures and runtime crashes caused by inconsistent symbol linking. Any insights or guidance from the community or Apple engineers would be greatly appreciated! Let me know if you'd like a shorter version or want to include additional build environment details (Xcode version, deployment target, etc.)!

I’m currently facing a disk space limitation on my Mac. I’ve already freed up some storage by following the suggestions shared in a previous post, which helped partially, but the issue is not fully resolved and space is still a bottleneck for my workflow. To move forward, I’d like to ask a very concrete question: Is it safe and supported to move Xcode to an external hard drive (SSD), use it from there, and simply connect the drive whenever I need to work with Xcode? Specifically: Are there known issues with performance, stability, or updates? Are there components that must remain on the internal disk to avoid unexpected behavior? Is this a reasonable long-term setup, or just a temporary workaround? I want to make sure I’m not setting myself up for hidden problems down the road. Thanks in advance for any clarification or best practices you can share.

We’ve encountered what appears to be a CoreML regression between macOS 26.0.1 and macOS 26.1 Beta. In macOS 26.0.1, CoreML models run and produce correct results. However, in macOS 26.1 Beta, the same models produce scrambled or corrupted outputs, suggesting that tensor memory is being read or written incorrectly. The behavior is consistent with a low-level stride or pointer arithmetic issue — for example, using 16-bit strides on 32-bit data or other mismatches in tensor layout handling. Reproduction Install ON1 Photo RAW 2026 or ON1 Resize 2026 on macOS 26.0.1. Use the newest Highest Quality resize model, which is Stable Diffusion–based and runs through CoreML. Observe correct, high-quality results. Upgrade to macOS 26.1 Beta and run the same operation again. The output becomes visually scrambled or corrupted. We are also seeing similar issues with another Stable Diffusion UNet model that previously worked correctly on macOS 26.0.1. This suggests the regression may affect multiple diffusion-style architectures, likely due to a change in CoreML’s tensor stride, layout computation, or memory alignment between these versions. Notes The affected models are exported using standard CoreML conversion pipelines. No custom operators or third-party CoreML runtime layers are used. The issue reproduces consistently across multiple machines. It would be helpful to know if there were changes to CoreML’s tensor layout, precision handling, or MLCompute backend between macOS 26.0.1 and 26.1 Beta, or if this is a known regression in the current beta.

Following an unexpected error message while working in Xcode, the project file xcodeproj is no longer synced in iCloud Drive. The Finder shows a cloud icon with a ! and an error message : (NSFileProviderErrorDomain error -2005.) If the local file is zipped, and unzipped elsewhere on iCloud Drive, then the unzipped file can still not be iCloud Synced. Restoring the file from a Time Machine archive does not solve the issue. Apple Care Support finds that iCloud Drive is working fine except for this xcodeproj file and says the issue is Xcode related.

I got accidentally this graph whilst playing with the periods of display in AppStoreConnect Trends hourly graph on several days But when I try to recall it, no way. If I select a multi days period, hourly graph is not available. Someone has an idea how to get it again ? Or was I lucky to profit of a forums bug ? Here are the settings for the graph I cannot select again.

Current issue (happening now) I get blocked immediately after entering my identity details and address. Apple Developer app (iPhone) I start the enrollment flow. After identity verification, I enter my address (Street Address, City/Town, State/Province, Postal/Zip, Phone). As soon as I tap Continue, I get: Contact Us to Continue There may be an issue with your account that needs to be resolved before you can continue. Please contact support. I cannot proceed past this point. Web enrollment (developer.apple.com) When I try on the web, I get: Your enrollment could not be completed. Your enrollment in the Apple Developer Program could not be completed at this time. This happens right after providing identity + address (before I can proceed further). Previous timeline (related background) ~3 months ago I incorporated my company in Türkiye (Ltd. Şti.) and tried to enroll as an organization. What happened First attempt on the web: enrollment was approved, but I couldn’t complete payment. Support told me to reset and try via the Developer app. Developer app enrollment then requested identity + “association with the enrolling entity” and company documents: Government-issued photo ID Employment/association verification Commercial registry extract (signed/stamped) Articles of association Tax office + tax number document Signatory circular I uploaded the requested documents. Apple replied that Turkish documents were unsupported and asked for “solicitor-certified English translations.” I uploaded English translations that were sworn-translator stamped. Why the translations were not notarized In Türkiye, due to the current economic situation, notarizing multiple translated corporate documents can cost hundreds of USD. Because of that, I initially provided sworn-translator certified (stamped) English translations rather than notarized translations. The translation office I worked with told me they regularly prepare company document translations for Apple Developer Program enrollments and that translator-certified translations are usually sufficient. My plan was to get everything notarized immediately if Apple explicitly requested notarization again or clarified that notarization was mandatory. About a week later, I received: Your enrollment request for your company has been declined. I followed up multiple times asking what exact requirement was not met (translation certification type, identity/association verification, etc.). Phone support said the decision was final and they could not disclose the reason. Additional detail discovered after the decline (document error fixed) After the decline, I reviewed all documents line-by-line and found a serious issue in my signatory circular: My company was incorporated on 27.08.2025. The signatory circular incorrectly stated that my authority started on 27.08.2023 (two years earlier). This was a notary/document preparation error. I immediately returned to the notary and had it corrected. They acknowledged the mistake, and I can obtain an official written statement confirming the correction if needed. However, Apple has not provided a channel to submit corrected documents, and support is not giving a path forward. What I’m asking the community Has anyone seen the “Contact Us to Continue” message triggered at the identity/address step and successfully fixed it? If yes, what specifically solved it? Is this typically an Apple Account eligibility/restriction flag, or can it be caused by address/region verification format issues? After an organization enrollment is declined, is there a known path to re-apply successfully (e.g., notarized translations vs translator-stamped, or having a different authorized representative apply as the Account Holder)? If documents were corrected after the decline (like the notary error above), is there any supported way to resubmit without starting from zero? Any concrete guidance would help. Thank you.