Is anyone else having issues uploading an archive to App Store Connect? I went to validate an archive of my app, and seems to hang during validation. I've tried just validating the app, and tried Transporter as well. It hangs on the analyzing app. How to troubleshoot?

Environment: Xcode 27.0 beta 6, Device Hub, tvOS 27.0 When focusing a TextField and using Device Hub to run on tvOS 27.0, I cannot type any text into the field. Focus moves to the TextField as expected, but keyboard input is not received. Has anyone else run into this? Any workaround would be appreciated.

I have been trying for 24 hours to upload app, and first time this has happened in 8 years and 100+ uploads. Please help. Validate App and Upload both hang indefinitely at "Preparing" in Xcode Organizer. No error is ever returned — the progress bar freezes and the operation never completes or times out. Transporter 1.4.5 fails identically. Key detail: archive 2.4.3 (build 123), which Apple accepted and processed on Sept 10, 2026, now hangs the same way when validated. Same machine, same Xcode, same Apple ID. This rules out the archive, its signature, and its provisioning profile. Already ruled out: two independent networks (home Wi-Fi and iPhone cellular hotspot); the archive itself (known-good build 123 fails identically); Xcode install (27.0 / 27A266a, xcode-select verified correct); Apple ID session (signed out and back in three times); full reboot. macOS 27.0 (26A428) on MacBookPro18,4. Last successful upload Sept 10, 2026. 100+ prior archives uploaded without incident over several years. macOS has updated twice since Sept 10. Separately: Transporter 1.4.5 crashes on macOS 27.0 with an unhandled exception in TransporterKit while drawing its activity queue (EXC_BREAKPOINT via +[NSApplication _crashOnException:]).

Xcode 27.0, watchOS 27.2, macOS 27.2. Re-pairing an Apple Watch Ultra 2 via Device Hub (File ▸ Pair Nearby Device…) completes successfully — remotepairingd logs setupManualPairing succeeded — but the watch never reconnects afterward: no verifyManualPairing, no _remotepairing._tcp Bonjour advertisement, and CoreDevice never creates a device record for it. devicectl shows the watch as unavailable, then it disappears from the list entirely. Compare: pairing an iPhone the same way also closes the setup channel within ~40 ms, but the iPhone reconnects ~1.3 s later via verifyManualPairing and becomes available. The watch never does. Interesting finding: if the Mac's pairing listener is kept open past the point where Device Hub's sheet would normally close it, the watch does come back — but it requests a brand-new pair-setup instead of verifying the one it just completed. It loops: setup → close → setup. Already tried without success: restarting the watch/iPhone, Developer Mode off/on, Bluetooth on/off, Wi-Fi toggles, iPhone on USB, restarting CoreDeviceService and remotepairingd, Reset Location & Privacy on the iPhone, updating watchOS (27.0 → 27.2, same behavior). Full write-up with sanitized logs, timeline and everything tried: https://github.com/kisnner26/watchos27-pairing-bug Filed as Feedback Assistant FB24924229. If anyone else hits this exact symptom (pairing succeeds, watch never reconnects — different from the PIN never appearing, or the watch never showing up at all, which are other variants reported elsewhere), please share your report ID here so Apple can link them.

In previous versions of Simulator.app, you could drag an unsigned iOS .app bundle onto the Simulator screen to install it. This was useful functionality to allow for more easy distribution of simulator-only builds within a team without needing to worry about signing and distribution. This functionality appears to have been completely removed in Device Hub which is a shame.

[Submitted as FB24979057] Device Hub is consistently crashing for me in Xcode 27.1. I initially encountered it while working in Xcode, but I can reproduce it completely independently of any project: Quit Xcode. Launch Device Hub directly. Wait a couple of seconds. Device Hub crashes. The latest crash occurred about two seconds after Device Hub launched, so this doesn’t appear to be related to a particular Xcode project. :chatgpt-content-reference{index="0"} Environment Xcode 27.0 (27A266a) DeviceHub 27.0 (255.2.6.6) macOS 27.0.1 (26A434) Apple silicon The crash is on the main thread during AppKit/SwiftUI layout and constraint updating: :chatgpt-content-reference{index="1"} :chatgpt-content-reference{index="2"} Exception Type: EXC_CRASH (SIGABRT) Termination Reason: Namespace SIGNAL, Code 6, Abort trap: 6 AppKit -[NSWindow(NSDisplayCycle) _postWindowNeedsUpdateConstraints] -[NSView setNeedsUpdateConstraints:] SwiftUI NSHostingView.setNeedsUpdate() NSHostingView.beginTransaction() AppKitPlatformViewHost.invalidateLayout() NSHostingView.SizeConstraints.update(from:) DeviceHub main Has anyone else seen this in Xcode 27.1 or found a workaround?

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

Apple M2 MacBook Pro 2022 (24GB/1TB) macOS 27.0 Xcode 27.0 Xcode hangs every time I try to open any xib file. Didn't face this issue in previous versions. I have attached some initial part of the report here, I have reported the problem via xcode too. Xcode hang.txt

在使用 xode 27 真机调试项目时 报了 ibrary 'd64' not found 这个错误， 这边有用到-ld64 遇到这个问题需要怎么去解决呢？ xcode 26 没有报这个错

what can i do?

The live Device Hub window shows my app's colors differently from a physical iPhone. The pixel values themselves are correct: a screenshot taken in Device Hub has the same colors as the device. Only the live window looks different — [e.g. more washed out / more saturated]. It happens in every project I've tried, including ones that use only plain sRGB colors and sRGB image assets, so it doesn't look app-specific. Setup Xcode 27.0 (27A266a) MacBook Pro, Apple M4 Max Built-in Liquid Retina XDR display (default "Color LCD" profile) and an external BenQ PD2705UA Simulated devices: iPhone 13 mini (iOS 26.1) and iPhone 14 (iOS 26.5) What I've ruled out Same result on both the built-in display and the external monitor True Tone and Night Shift are off on the Mac The simulated device is in light mode, with Increase Contrast, Invert Colors and Grayscale off The Device Hub screenshot matches the physical iPhone, so the rendered pixels are correct Questions Is the Device Hub window color-managed for the Mac's display, or is this expected behavior? Is there a setting to make the live window show accurate colors?

I am using Coding Intelligence, powered by Claude, in the first production release of Xcode 27.0 (in MacOS 26.7). Initially it was working ok. But after less than a day, it now crashes every time it needs to ask for permission for any shell command. And each time I restart things, it burns through a ton of tokens. ☹️ Any suggestions? (I'll file a bug report right now…)

I’m blocked debugging a watchOS app on a physical Apple Watch. The iPhone connects to Xcode normally (wired), but the Watch either fails to connect with a tunnel timeout or disappears entirely from Xcode after I unpaired it inside Devices & Simulators. Environment Mac: macOS 26.x (Apple Silicon Mac) Xcode: 26.2 iPhone: iOS 26.1 Apple Watch Ultra: watchOS 26.2 (build 23S303) Connection: iPhone connected to Mac via USB (trusted). Watch paired to iPhone and working normally in the Watch app. Issue A (when Watch is visible in Xcode) In Xcode → Window → Devices and Simulators, the Watch shows up but is not usable and fails to connect. Error: “Previous preparation error: A connection to this device could not be established.” “Timed out while attempting to establish tunnel using negotiated network parameters.” In some attempts the Watch shows “Capacity: Unknown” / limited details, and then fails during preparation. Issue B (after unpairing Watch in Xcode only) I unpaired/removed the Watch in Xcode (Devices & Simulators). I did not unpair the Watch from the iPhone. Now: iPhone appears in Xcode and works normally for builds. Watch is still paired to the iPhone and works normally. Watch no longer appears anywhere in Xcode Devices & Simulators (no paired watch section, no watch run destination). What I’ve tried Reboots of Mac, iPhone, Watch (multiple times) Watch unlocked, awake; iPhone unlocked and close to Watch Verified Watch is paired and connected in iPhone Watch app Developer Mode enabled on iPhone and Watch Wi-Fi and Bluetooth ON (Mac/iPhone/Watch), tried toggling both Tried on home Wi-Fi and also with iPhone hotspot (same result) Resetting trust prompts / reconnecting iPhone via USB, re-trusting Mac Apple Watch: “Clear Trusted Computers” Xcode: removing/re-adding devices; clearing derived data; restarting Xcode Watch Developer networking test: Responsiveness = Medium (430 RPM) Questions 1. Is this a known issue/regression with Xcode 26.2 + watchOS 26.2 tunneling (CoreDevice / devicectl)? 2. Is there an Apple-supported way to force Xcode to re-discover a paired Watch after it was removed from Xcode Devices & Simulators (without unpairing the Watch from the iPhone)? 3. Any recommended logs or diagnostic steps I should collect (Console logs, sysdiagnose, specific Xcode/CoreDevice logs) to include in a Feedback report? If helpful, I can provide the full error text from Xcode’s Devices window and any logs you recommend. Thank you in advance,

I wanted to test my App for Apple TV and iPad/iPhone with a DualShock 2 game controller. This worked perfect with the former Xcode version. Now nothing happens, if I use the game controller. In blue tooth is is connected and if I use my game without Device Hub it is also working. Additionally it is nearly impossible to debug my game on Apple Watch with the Digital Crown, it takes minutes to start the simulators for iPhone, my Mac is getting extremely hot, ... Is there a possibility to use the old simulator? Device Hub is not really usable for developers.

Hi everyone, Is anyone else having problems with Xcode 27? It keeps crashing on me. And when I say ‘constantly’, I mean it shuts down about every minute. You can’t work like this... Am I the only one with this problem?

I have two apps; one is a subset of functionality of the other. The smaller app has about 170 Swift files. The larger app has these files plus about 120 more. So I would expect the larger app to take around twice as long to build. Instead, the smaller app takes less than a minute to build while the larger app takes over 13 minutes to build; to be exact, it takes 15.3 times longer. While reviewing the build report, I noticed that the smaller app compiles the Swift files in batches, with each batch taking around 10 seconds, but with up to 17 batches running at once. In contrast, the larger app compiles all 290 Swift files in one giant batch, so apparently there is no multithreading of the Swift compilation (see screen shots below). The difference in the number of batches the smaller app compiles at once roughly corresponds to the difference in overall build time. Is there a build setting I can change to make the larger app compile Swift files in multiple smaller batches as the smaller app is doing? I checked SWIFT_COMPILATION_MODE and it's the same in both apps (Incremental for debugging and Whole Module for release) but I don't know what other settings I should check.

A Mac reboot fixed it for a few images, but then it went black again.

Has anyone notices persistent UI lockups when attempting to perform even the most basic tasks with Claude Code? I'm at a total loss here. I've noticed that the lockups tend to happen more often when the Claude Agent is asking me a question. I've tried removing stale data, disconnecting / reconnected the agent, force quit and restart. Nothing solves this.

Hi, I’m trying to test an independent watchOS app on an Apple Watch Series 6 Cellular that is set up for a child using Apple Watch For Your Kids (Family Setup). My current environment: Apple Watch Series 6 Cellular watchOS 26.6 The Watch is set up for a child using Apple Watch For Your Kids / Family Setup Xcode 26.6 Parent iPhone running iOS 27.0 Developer Mode is enabled on the parent iPhone The Family Setup Watch does not appear as a development device in Xcode/CoreDevice There is no Developer Mode option visible on the Family Setup Watch For comparison, I also have another Apple Watch used for normal development, and that Watch can be detected by the development environment. The issue appears specific to the child’s Family Setup Watch. I would like to understand the Apple-supported development and testing workflow for this configuration. Specifically: Is an Apple Watch set up using Apple Watch For Your Kids / Family Setup expected to be available as a direct Xcode development device? If direct Xcode deployment is not supported, can an independent watchOS app be installed and tested on a Family Setup Watch through TestFlight? If TestFlight is supported, what is the correct workflow for installing the beta on the child’s Family Setup Watch / child Apple Account? Is there another Apple-supported testing or distribution method developers should use for this scenario? I’m specifically asking about an independent watchOS app that can operate without the parent iPhone nearby, rather than a Watch app that depends on an iPhone companion app. I’d also appreciate clarification on the distinction between direct Xcode development deployment and TestFlight/App Store distribution for Apple Watch For Your Kids. Thank you.

Hello, I am playing around with MailKit in Xcode... just created a new App with MailExtension target. When I run it, it's asking if I want to test it with Mail, however, I cannot see the extension in the Mail Settings for enabling it... I a totally newbie here.... what am I missing?