When resizing using Device Hub, it becomes completely black and gets stuck at 2560 × 1440.

i'am still getting crash while testing dotnetmaui my app, here is my environment info and crash report @shanselman macOS Tahoe 26.5, macOS Rider 2026.1.2 dotnet workload list Workload version: 10.0.300.3 Installed Workload Id Manifest Version Installation Source ios 26.5.10284/10.0.100 SDK 10.0.300 maccatalyst 26.5.10284/10.0.100 SDK 10.0.300 maui-android 10.0.20/10.0.100 SDK 10.0.300 maui-ios 10.0.20/10.0.100 SDK 10.0.300 xcodebuild -version Xcode 26.5 Build version 17F42 crash-report.txt

Is there a known workaround (other than forking) for watchOS builds in Xcode 27 that depend on packages without a declared watchOS 9.0 floor? I depend on several Apple SPM packages with no minimum deployment target, such as https://github.com/apple/swift-algorithms. My project's minimum is 26.0. Xcode 27 will not build watchOS targets with these packages because watchOS 8.0 is below its range of supported targets. /.../SourcePackages/checkouts/swift-algorithms/Package.swift The watchOS Simulator deployment target 'WATCHOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 27.0.x.

Overview When a project contains SwiftData and the Preview uses a in memory database, SwiftUI preview doesn't show the data Have a look at the ContentView preview Environment Xcode 27.0 beta (27A5194q) 26.5.1 (25F80) Feedback FB23041713 Please can you have a look at the feedback, it also has a sample project and screenshot

I am writing this as a final attempt to get some clarity regarding my app review. My app, Wecheerup 360 Booth (App ID: 676214516, Bundle ID: com.wecheerup.wecheerup360booth.ios), entered the review process on April 15, 2026. As of today, it has been in "In Review" status for nearly two months. What frustrates me is not the waiting time itself. I understand that reviews can take longer in some situations. What is becoming extremely frustrating is the complete lack of information. There are no messages in the Resolution Center. There are no requests for additional information. There are no indications that something is wrong with the app. There is simply a status that says "In Review" and nothing else. I have contacted Apple multiple times during this period. Every response I receive appears to be the same generic template stating that my app has not been forgotten and that the review is still ongoing. Whenever I ask specific questions, such as whether there is an issue with the app, whether additional information is needed, or whether there is any estimated timeline, those questions go unanswered. At this point, I feel completely stuck. I joined the Apple Developer Program specifically to publish this application. Since submitting version 1.0.3 on April 13, I have continued developing the product and have already implemented new features and newer versions. The app itself has evolved significantly while the original submission remains indefinitely in review. What I am asking for is not expedited review. I am not asking for special treatment. I am simply asking for communication. If there is an issue, please tell me. If additional review is required, please tell me. If there is a reason for the delay, please tell me. After nearly two months, receiving only generic responses and seeing no activity whatsoever in App Store Connect is incredibly discouraging. I genuinely like developing for Apple platforms, but this experience has been one of the most frustrating developer experiences I have had. Not because of the wait itself, but because there is no transparency, no feedback, and no indication that anyone is actually looking at the case. I would sincerely appreciate any clarification regarding the status of this review.

using String Catalog, missing locale entries don't fall back to source language. for example, "%lld videos" : { "comment" : "Label for a number of videos", "extractionState" : "manual", "localizations" : { "en" : { "variations" : { "plural" : { "one" : { "stringUnit" : { "state" : "translated", "value" : "%(count)lld video" } }, "other" : { "stringUnit" : { "state" : "translated", "value" : "%(count)lld videos" } } } } }, this allows us to use Text(.videos(count: 1)) in English and it'll produce "1 video" as expected but when the locale is French for example, it'll produce "1" instead, until "fr" entry will be added. this is extremely inconvenient. what's the proper workaround?

Glancing through this forum, this seems to be a recurrent pattern sigh. Symbols for watchOS 26.5 (23T570): Failed with HTTP status 403: Forbidden. Nibbling them over wireless doesn't work either, since after 1h or so, the connection just fails and never resumes. watchOS development platform is the worst experience since I started developing on C64 in 1983.

I was playing around with the brand-new reorderable API and couldn't get it to work within previews. Is there a specific way to get previews to work with reorderable, or do I need to compile every time? I was also curious if there will be an addition to the Array generic struct, as it seems like the solution there currently is is just an extension, although the way it's being promoted makes it seem like it is built into the type.

I have a large dictionary of words in an app that I’d like to localize. I'm thinking of asking a human translator (or AI agent) to translate them. I might translate each word by machine and include the translation in the data I provide to the translator as candidates. How can I export this data to the translator in XLIFF format? Does iOS have API for XLIFF generation or interpretation? Are there decent open source options written in Swift?

Our app lets users pick the locale for a particular document (macOS document-based AppKit), then produce outputs using various inputs (user-provided and others) in that locale. We've written much of the plumbing, but are getting really close to String Catalogs and the like. What can we do to use AppKit and Xcode's localization tools correctly and efficiently in this case? We already have "Localization" objects, and are splitting the work into multiple String Catalogs for clarity. In each case the app will need to use the given Localization to produce (or replace) text at runtime, including the result of formatters

Is there documentation or a video for -[NSString initWithValidatedFormat:validFormatSpecifiers:locale:error:] and similar APIs?

I'm amazed by agentic coding presented in the "Translate your app using agents in Xcode" session. Does agentic translation support localized strings contained in Objective-C modules? Does it support strings in Interface Builder XIBs?

Hey, anyone figured out how Device Hub will work? I have a Mac OS 26.5.1 (25F80) version. It's not working with my device configurations. I have downloaded Xcode components of Xcode 27 and iOS 27 simulators, but device help seems to be not working. If anyone has a similar problem or has a fix, kindly let me know.

Hi, thanks for offering this Q&A! We've always used real translators for our apps, but recently our vendor went out of business, and this WWDC is focusing heavily on agentic localization. It's clear this is where the industry is trending, but we're worried about our user experience if we have a fully AI-driven localization. How do you recommend verifying that agentic localization output is correct, friendly, appropriate, etc?

I have raised Feedback FB23036084 Just using it on an extremely small app that display six SwiftUI charts. I was just scrolling on a ScrollView of the charts. Th feedback has a link to the app on GitHub, the content of the generate report details and also the output of running xcrun simctl diagnose

I can’t make or edit new feedback or drafts, this just shows up or it takes too long to load.

When compiling the codebase with Xcode 27 and running it on a simulator or real device (with iOS 27 or iOS 26.x) the app keeps crashing in certain situations with the error "Thread 1: EXC_BAD_ACCESS (code=257, address=0x80000001097a409e)". The exact same codebase is working just fine on Xcode 26.5. I’ve tested changing the Xcode 27 toolchain to a custom one (6.3.2) but it still crashes. I’ve also tried to usual steps to delete the derived data folder and clear the cache. Nothing worked. Here's the Feedback ID I've opened: FB23035297. Is this happening to anyone else? Any idea?

Every time I try to login to my Anthropic account after pressing 'Sign In...', nothing appears to happen and cannot move past the Sign In... dialogue. The sign in screen appears and I can press 'Authorize' but nothing changes. Any tips on how to login to use Anthropic over OpenAI?

Summary: After upgrading to Xcode 26.4, app-hosted XCTest execution on physical devices running iOS 16 fails at test-planning time with "Logic Testing Unavailable." The same project and same device work under Xcode 26.2. The failure reproduces with a standalone minimal Xcode project, which suggests this is an Xcode regression rather than a project-configuration issue. Environment: Xcode: 26.4 (17E192) macOS: Tahoe 26.4 Failing device: iPhone 11 (iPhone12,1), iOS 16.0.3 Working comparisons: Xcode 26.2 + same iPhone 11 (iOS 16.0.3): works Xcode 26.4 + iPad Pro 11-inch (4th generation) on iOS 26.3: works Regression: Yes. Works on Xcode 26.2. Fails on Xcode 26.4. Same project, same signing setup, same physical iOS 16 device. Minimal reproduction: A minimal sample project with: one iOS app target one app-hosted unit-test target one UI-test target (for comparison; not required to reproduce) Steps for the unit-test repro on a physical device running iOS 16: Build for testing: xcodebuild -project TestProject.xcodeproj \ -scheme TestProject-UnitTests \ -sdk iphoneos \ -destination 'platform=iOS,id=<DEVICE_UDID>' \ -derivedDataPath DerivedData-Device-Unit \ -resultBundlePath Results-Device-Unit-Build.xcresult \ DEVELOPMENT_TEAM=<TEAM_ID> \ CODE_SIGN_STYLE=Automatic \ build-for-testing Run tests without building: xcodebuild -project TestProject.xcodeproj \ -scheme TestProject-UnitTests \ -sdk iphoneos \ -destination 'platform=iOS,id=<DEVICE_UDID>' \ -derivedDataPath DerivedData-Device-Unit \ -resultBundlePath Results-Device-Unit-Test.xcresult \ DEVELOPMENT_TEAM=<TEAM_ID> \ CODE_SIGN_STYLE=Automatic \ test-without-building Note: xcodebuild test (combined build and test) also fails with the same error. Expected result: The hosted unit tests run successfully on the connected physical device, as they do under Xcode 26.2. Actual result: Step 1 (build-for-testing) succeeds. Step 2 (test-without-building) fails immediately (within ~1 second) with: 2026-03-26 11:23:28.683 xcodebuild[51930:731004] DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. 2026-03-26 11:23:28.725 xcodebuild[51930:730966] [MT] DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. 2026-03-26 11:23:29.239 xcodebuild[51930:730966] Writing error result bundle to /var/folders/jl/knmkq18x4cg_3w087zgpfldm0000gn/T/ResultBundle_2026-26-03_11-23-0029.xcresult xcodebuild: error: Failed to build project TestProject with scheme TestProject-UnitTests.: Cannot test target “redacted” on “redacted”: Logic Testing Unavailable Logic Testing on iOS devices is not supported. You can run logic tests on the Simulator. Why this looks like an Xcode regression: The same project and same physical iOS 16.0.3 device work under Xcode 26.2. Under Xcode 26.4, build-for-testing still succeeds, so signing, provisioning, and bundle construction appear valid. The failure happens only when Xcode plans or launches the on-device test run. Before the failure, Xcode 26.4 logs: DVTDeviceOperation: Encountered a build number "" that is incompatible with DVTBuildVersion. A newer physical device running iOS 26.3 works under Xcode 26.4 without this warning. The issue also reproduces with a minimal standalone Xcode project, which makes a project-specific configuration problem unlikely. The Xcode-generated .xctestrun files for the passing Xcode 26.2 case and failing Xcode 26.4 case are structurally equivalent, making an .xctestrun format difference unlikely to be the cause.

Environment: MacBook Air M4 macOS 27 Golden Gate Beta Xcode 27 Beta iPhone running iOS 27 Beta Apple Watch Series 10 paired to the iPhone Steps to Reproduce: Install macOS 27 Beta and Xcode 27 Beta. Pair an Apple Watch with an iPhone running iOS 27 Beta. Enable Developer Mode on the iPhone. Connect the iPhone to the Mac and launch Xcode. Open Window → Devices and Simulators. Attempt to locate the paired Apple Watch or enable Developer Mode on the watch. Expected Result: The paired Apple Watch appears in Xcode for development purposes. A Developer Mode option is available on the Apple Watch. Xcode is able to recognize and communicate with the watch through the paired iPhone. Actual Result: The Apple Watch does not appear in Xcode. No Developer Mode option is visible on the watch. The iPhone is successfully paired and running iOS 27 Beta, but the watch remains unavailable for development workflows. Additional Notes: The iPhone and Apple Watch are already paired and functioning normally. Developer Mode is enabled on the iPhone. Restarting devices and reconnecting the iPhone did not resolve the issue. Unsure whether this is a limitation of the current beta builds or a regression in Xcode/watchOS development tooling.