“Xcode”

Filed here: FB22276321 (Xcode Cloud build encountering persistent Connection Refused error)

Do these IP's ever change? Rarely, but it does happen. The list you see was recently updated, and these changes are announced through the Xcode Cloud Release Notes, so you can see when the recent update happened. Are there specific ports Apple uses? Would be nice to limit to only what's needed. None are documented, so you shouldn't make any assumptions about port selection. Do we have to open in-bound access or can we instead have our builds reach out with an outbound only setup? Xcode Cloud requires inbound access, that is noted in the document you linked to very briefly. — Ed Ford,  DTS Engineer

By contrast, I can sign in to the Sandbox Apple Account without issue on a physical device. The problem occurs only via Simulator. That is the expected behavior. To test in the sandbox environment, you need a physical device. For more information, see Testing In-App Purchases with sandbox. StoreKit Testing in Xcode is a local test environment for testing in-app purchases without requiring a connection to App Store servers. You can use it to test In-App Purchases in the Simulator without a Sandbox account.

Hi @Ziqiao Chen and everyone, Thank you for the follow-up. You were right to push for more precise testing — it led me to discover an issue with my original test setup and reach a much clearer understanding of the problem. == Correction: Original Test Setup == My initial frontmost test had a build configuration error: the test build still had an active HKWorkoutSession running in the background. This means the results I would have reported (~10 minutes before termination) did not reflect pure frontmost app state behavior. I've since corrected this and re-tested with precise instrumentation. == Hardware & Software == Apple Watch Series 8 (45mm) — not Series 4 watchOS 11.6.1 (latest stable) Build: Debug, standalone watch app Xcode debugger disconnected before all tests (to avoid priority elevation) == Methodology == I added a 30-second heartbeat timer that logs: Sequential counter and elapsed seconds Current heart rate value and time since last HR sample (hr_age_sec) App lifecycle transitions (Scen

Yes, both are signed Executable=/Users/alexf/Library/Developer/Xcode/DerivedData/Passthrough-fmtxodvbsknmqegwvscnzsczlopk/Build/Products/Debug/PassthroughAppEx.appex/Contents/MacOS/PassthroughAppEx Identifier=com.example.apple-samplecode.PassthroughXXXXXXXX.AppEx Format=bundle with Mach-O thin (arm64) CodeDirectory v=20400 size=476 flags=0x0(none) hashes=3+7 location=embedded Hash type=sha256 size=32 CandidateCDHash sha256=9abcde7d8b79d23164600c46c55cdace7136690a CandidateCDHashFull sha256=9abcde7d8b79d23164600c46c55cdace7136690aecb06f89082b53853a045b76 Hash choices=sha256 CMSDigest=9abcde7d8b79d23164600c46c55cdace7136690aecb06f89082b53853a045b76 CMSDigestType=2 CDHash=9abcde7d8b79d23164600c46c55cdace7136690a Signature size=4781 Authority=XXXXXXXXXXXXX Authority=Apple Worldwide Developer Relations Certification Authority Authority=Apple Root CA Signed Time=17 Mar 2026 at 15:00:17 Info.plist entries=21 TeamIdentifier=XXXXXXXX Sealed Resources version=2 rules=13 files=3 Internal requirements count=1 si

Same issue for me as well and my ability to test on a real device is totally blocked and has been actually since some time back in Nov.! Xcode 26.3 iOS 26.3.1 watchOS 26.3 Watch was paired to Xcode but would never connect due to the same tunneling errors mentioned by others. After unpairing via Xcode Devices and Simulators the watch cannot be repaired even though I have unpaired and repaired it with iPhone and unpaired and repaired the iPhone to Xcode. NOTHING will cause Xcode to find the watch again. Damn it Apple this crap has been an ongoing issue since Xcode 26.0 How do you have 3 dot releases and not fix something like this?! Might have gotten the watch re-connected via another suggestion in higher up in this thread to connect mack to iPhone via Hotspot. I can see the watch again in Devices and Organizers, but the setup is taking foreeeeeevvverrr so not sure what happen when I switch the mac back to regular wifi.

@DTS Engineer I have created fresh virtual machine with latest macOS, installed latest Xcode there and check. Behavior is still broken (check video below). https://drive.google.com/file/d/1THJ-o_4htaP2FvH8w4nt8IsbIsNefgZk/view?usp=sharing As you requested, I've also collected sysdiagnose: https://drive.google.com/file/d/1xv11WVYlVjCEVmggr37cETbqd-5w8Yyd/view?usp=sharing

[quote='880415022, ToshiyukiTakeda, /thread/819261?answerId=880415022#880415022, /profile/ToshiyukiTakeda'] Will the Entitlements field for Team ID NWKYYYYYYY be added if I simply wait? [/quote] Our records show that Team ID NWKYYYYYYY already has access to the entitlements need to use NEAppPushProvider. In Xcode’s Signing & Capabilities editor, it should show up as Network Extension (additional values). Likewise in the App ID editor on the Developer website. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I am unable to download the specified version 26.2. In light of the issue discussed in this thread: https://developer.apple.com/forums/thread/818209, could this be related to the local Xcode version? yue22.chen@L7JF2KDP9J code % xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26.2 Finding content... iOS 26.2 is not available for download. yue22.chen@L7JF2KDP9J code % xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26.2.0 Finding content... iOS 26.2.0 is not available for download. yue22.chen@L7JF2KDP9J code % xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion iOS26.2 Finding content... iOS iOS26.2 is not available for download.

Thank you very much for your patient response. However, I think my situation was different. After carefully reading the developer documentation, I realized that I hadn't added the Hotspot Configuration Entitlement to my certificate, which caused code 8 to appear. This issue was unrelated to the system version or device model. After I added the entitlement in Xcode, everything started working normally. Here is the link to the documentation, hoping it can help others: https://developer.apple.com/documentation/BundleResources/Entitlements/com.apple.developer.networking.HotspotConfiguration Nevertheless, I still think it would be better if the error message for missing permissions could be isolated, providing a clearer hint to developers.

I have the same issue using Xcode 26.2. No issues with Xcode 26.3. FB22265099

Please file a feedback report via Feedback Assistant and share the feedback number here once submitted. Include the OS, Xcode versions and sample code you're able to reproduce the issue on.

Thanks for this interesting post! I'm not an expert on that field nor that API. Hope one of the engineers on that team can jump into this thread for better info. These specific FigXPCUtilities and FigCaptureSourceRemote logs are almost certainly benign internal framework noise rather than a regression or a flaw in your capture pipeline. Looking up the err=-17281 is a CoreMedia error code that, without knowing here, typically points to a minor XPC synchronization hiccup, a port invalidation, or an asynchronous state mismatch during the setup or teardown of the capture session? I believe this logs are for information only and should be removed. Code paths that silently recovered in older iOS versions often have their log levels elevated in newer releases (or beta releases), resulting in console spam. If your AVCaptureVideoDataOutputSampleBufferDelegate is successfully receiving CMSampleBuffer frames and your preview layer is rendering smoothly. You can safely ignore these logs. If you want to temporarily hide t