What is Apple’s supported way to prevent outbound network access during app-hosted iOS Simulator unit tests, without disabling system services or modifying system tunnel routes? Environment: Apple silicon Mac, macOS 26.6.2 Xcode 27.0, iOS 27.0 Simulator Separate, newly created Simulator Xcode-managed local ad-hoc build 17 fictional-data tests using XCTest and Swift Testing We intend to use xcodebuild test-without-building. The test bodies exercise models and request construction without sending requests, but the app host’s startup behavior is also within our isolation requirement. Tests have not been run. During an authorized Wi-Fi-off diagnostic, we waited ten seconds and collected three samples, checking Wi-Fi power before and after each sample. All showed: Wi-Fi Off No effective network interface reported by scutil --nwi No route selected by ordinary local lookups for IPv4 and IPv6 documentation addresses Remaining interface-scoped IPv6 default entries through utun interfaces Routes selected when IPv6 lookups explicitly specified those tunnel interfaces These were routing-table queries only; no diagnostic packets were sent. Wi-Fi was restored afterward. We have not established whether the scoped routes could carry external traffic. Please advise on a supported isolation mechanism and how to validate it for the Simulator test host, including startup. We want to preserve normal macOS security/system services and avoid relying on either route-table presence or absence as proof of isolation. No real user data or credentials are needed. We can provide a redacted diagnostic summary if useful.

I'm trying to use Xcode Coding Assistant connected to local AI server, but the chat fails after 5 minutes with error: The request timed out. Detail: No Data/Bytes for request: http://localhost... AI server gives me info that client disconnected: 2026-10-19 22:24:23 [INFO] [nvidia/nemotron-3.5-super-vl] Prompt processing progress: 88.3% 2026-10-19 22:24:30 [INFO] [LM STUDIO SERVER] Client disconnected. Stopping generation... (If the model is busy processing the prompt, it will finish first.) 2026-10-19 22:24:30 [INFO] [nvidia/nemotron-3.5-super-vl] Finished streaming response 2026-10-19 22:24:31 [DEBUG] 17.12.133.523 W srv stop: cancel task, id_task = 0 2026-10-19 22:24:37 [DEBUG] 17.18.441.198 I slot release: id 0 | task 0 | stop processing: n_tokens = 47985, truncated = 0 It looks like http/tcp default timeout. AI suggests that it should be possible to set Xcode Coding Assistant timeout, but I cannot find it anywhere. How is Xcode Coding Assistant supposed to work if it shuts down on default network protocol timeout? I haven't tried yet on nVidia hardware, which should be faster, but it could still be a problem when working on multiple files in project with inference running on one Blackwell chip. I do not have nVidia rack with 72 chips, it wouldn't fit to my home office. How do I change the network timeout for Coding Assistant? Configuration: MacOS 27.0.1 (26A434) Xcode 27.0

I'm hitting a toolchain inconsistency between Xcode 26.3's asset compiler (actool) and App Store Connect's upload validator, and I have build logs proving both sides. The builder side (actool in Xcode 26.3): When compiling the asset catalog for our watchOS target, actool reports "unassigned children" for the watchOS longLook icon role - specifically [watch][44x44][longLook][42mm][2x] - and does NOT compile it into Assets.car. The 42mm longLook icon simply cannot be produced by the toolchain. The checker side (App Store Connect): Uploading the resulting archive is REJECTED by the App Store Connect validator with a "Missing Icon" error for a 44x44 at 2x image (Long Look 42mm). So the builder cannot produce the exact icon the checker demands. This is an Apple toolchain inconsistency - either: actool should compile the longLook 42mm role into Assets.car, or the App Store Connect validator should not demand an icon the toolchain cannot emit. Environment: Xcode 26.3 watchOS app target with an App Icon asset catalog containing the longLook role configured for 42mm 2x Question: Is this a known issue, and is there a workaround to produce an upload that passes validation? I can provide build logs for both sides on request.

Hello everyone, I am currently building an app using Base44 and want to bring my project code over into Xcode so I can implement StoreKit in my app for IAPs. Since I am new to moving a web/external project setup into Xcode's native environment, I was hoping to get some guidance on the best workflow. What is the recommended way to structure or import a Base44 project into Xcode? Are there any specific configuration steps or file adjustments required so that Xcode recognizes the source files properly? Once imported, are there any "gotchas" to keep in mind when setting up StoreKit configurations within the new Xcode project? Any advice, tips, or step-by-step pointers would be greatly appreciated! Thanks in advance.

Xcode 27 keeps failing to download the Documentation, it shows "Preparing to download" and spins the camomile endlessly. I checked logs (with help of AI) and found this: Xcode queries com.apple.MobileAsset.AppleDeveloperDocumentation. Metadata catalog loading suceeds. Then asset resolution loops with: MAQueryTooManyResults - Asset load result ... 13 (MAQueryTooManyResults) Also CSSMERR_CSP_VERIFY_FAILED from mobileassetd during this sequence. In my /System/Library/AssetsV2 I have 3 old .asset files all from Xcode 26, the last one updated on Jun 12. But I don't think it's the reason for the error. What would you suggest to recover the documentation?

iPhoneSimulator.app used to have the ability to show an external display / CarPlay display, but this feature does not appear to be available in DeviceHub.app, making it difficult (/impossible :( ) to test CarPlay features from the simulator.

I’m seeing a reproducible iPhone Duo Simulator boot failure in Xcode 27.1. Environment Xcode 27.1 / 27A9275 macOS Tahoe 26.6.2, then 26.7.1 Apple silicon Mac iPhone Duo / V68 / iPhone19,4 iOS 27.1 Simulator Runtime builds 24A94232 and 24A94425 Failure Running: xcrun simctl bootstatus -b terminates with: Status=3, isTerminal=YES Data Migration Failed Fresh Duo devices reproduced the failure on both runtime builds. During fresh migrations, DataMigrator logged: Reporting migration failure due to migration progress window incident On one fresh-device run, all 35 recorded migration plugins completed successfully, but the aggregate migration result was false and no failed-plugin identifier was exposed. I also tested: brand-new Duo simulator data restarting the correct CoreSimulatorService explicitly selecting runtime 24A94425 updating macOS from 26.6.2 to 26.7.1 An ordinary iPhone simulator on iOS 27.0 works on the same Mac. The failure occurs before any application is installed or launched. Feedback filed: FB25221101 Has anyone else seen this with the iPhone Duo Simulator in Xcode 27.1?

I created a new Project on Xcode 16 on macOS Sequoia and connected it to a GitHub repository. After making a change on a sub branch, I opened a pull request. On GitHub I can see the changes I made in a diff view. However when I select the PR in Xcode and click on "View Changes" all I get is a endless spinning activity indicator. I could not find anything that would explain this behavior. Any help very welcome.

I got this error when using iPhone Duo Simulator on Xcode 27.1 iPhone Duo’s iOS Simulator platform doesn’t match App.app’s supported platforms. You can change App.app’s Base SDK or Supported Platforms to support iPhone Duo. My Supported Platforms is already iOS. How to fix this one properly?

Hello, I started writing my app on Xcode 26 and everything worked super smoothly. A build would take less than a minute and would immediately open the app on my iPhone 13 Pro. After updating to XCode 27 a build would still finish in the same amount of time, but it would only open the app maybe once out of 10 attempts, most of the time though nothing happens. No matter how long I wait, if I disconnect, reconnect, unlock my phone, it seems like xcode doesn't even notice. I display the build time inside the app and when I manually open the app I can see that it's from the last time the build successfully launched the app automatically. So it's stuck somewhere between building and loading it onto my phone I assume. I recently updated my phone to an 18 Pro and the issue persists. Connection is via USB-C cable. Anyone have any suggestions what might be wrong? Thank you!

I just purchased the Apple Developer Paid Account on the 3rd of October to start development on an App and hasn't been able to use it even once I’m having an iOS code-signing/provisioning issue where development/Ad Hoc builds complete successfully, but the app cannot be installed on my registered iPhone. The same issue occurs with builds produced through both Xcode and Expo EAS Build, so at this point I don’t think this is specific to EAS. When installing the app on the device, iOS shows: Unable to Install “Sencard” This app cannot be installed because its integrity could not be verified. The device logs give a much more specific error. Environment Apple Developer account type: Individual Team ID: 26K9NDX728 Main bundle identifier: com.sencard.mobile Widget extension bundle identifier: com.sencard.mobile.widgets App Group: group.com.sencard.mobile Physical iPhone registered in the Apple Developer portal Expo SDK: 57 EAS distribution: Internal / Ad Hoc The same device is included in both provisioning profiles The issue also occurs when building/installing through Xcode The application contains a WidgetKit extension, so there are two targets: Sencard com.sencard.mobile ExpoWidgetsTarget com.sencard.mobile.widgets Both targets use the same Apple Distribution certificate, with separate provisioning profiles as expected. Current signing configuration I completely reset the signing credentials and let EAS regenerate them. Both targets now use the same distribution certificate: Distribution Certificate Serial: 64FE74F9A8F0091A81671D9CDE9F7CDB The main application has its own active Ad Hoc provisioning profile: Bundle ID: com.sencard.mobile Provisioning Profile: 7D9CS7B97R Status: active Registered device: included The widget extension has a separate active Ad Hoc provisioning profile: Bundle ID: com.sencard.mobile.widgets Provisioning Profile: DY3D63UHPX Status: active Registered device: UDID: 00008130-************001C EAS reports: All credentials are ready to build @sencard/sencard (com.sencard.mobile, com.sencard.mobile.widgets) The build itself completes successfully. Device-side failure I captured the device system log while reproducing the installation failure. The important part appears to be Apple’s online provisioning authorization service rejecting the profile: online-auth-agent: The server returned: {"actions":["REJECT_PROFILE"],"authorized":false,...} online-auth-agent: Permanently rejected profile This is immediately followed by: installd(libmis.dylib): No online authorization (0x2) installd(libmis.dylib): validation failed because of failing online authorization (-402620392) Then MobileInstallation reports: The identity used to sign the executable is no longer valid. and: Failed to verify code signature of .../Payload/Sencard.app 0xe8008018 (The identity used to sign the executable is no longer valid.) Finally: Verification stage failed and the installation fails. What seems particularly significant is that the device contacts the online authorization service successfully, but the response is explicitly: "actions":["REJECT_PROFILE"] "authorized":false Things I have already tried I have done a fairly extensive clean reset of the signing configuration: Deleted the existing Ad Hoc provisioning profiles. Removed the existing distribution certificates from EAS. Revoked the corresponding distribution certificates in the Apple Developer portal. Created a completely new Apple Distribution certificate. Generated completely new Ad Hoc provisioning profiles. Verified that the provisioning profiles show as active in EAS. Verified that both profiles contain the physical iPhone being used for testing. Verified that both targets belong to Apple Team 26K9NDX728. Configured both the main app and widget extension to use the same distribution certificate. Created separate provisioning profiles for: com.sencard.mobile com.sencard.mobile.widgets Confirmed the App IDs still exist in the Developer portal. Confirmed the App Group exists and is assigned correctly. Confirmed the registered iPhone is present in the Developer portal. Rebuilt the app from scratch after regenerating all credentials. Confirmed that the EAS build succeeds. Reproduced the installation failure again on the physical device. Captured the iPhone system logs using idevicesyslog. Reproduced the problem with Xcode as well as EAS. Initially, before resetting the credentials, I also encountered a build-time error similar to: Provisioning profile ... doesn't include signing certificate "iPhone Distribution: ... (26K9NDX728)" I then deleted and regenerated the certificates/profiles and ensured both targets shared the same distribution certificate. That resolved the build failure — the application now builds successfully — but the resulting application is still rejected by iOS during installation with the REJECT_PROFILE / 0xe8008018 error above. What I’m trying to determine Is there some server-side state associated with my Apple Developer team/account that can cause a newly generated, apparently valid Ad Hoc provisioning profile to be returned as: REJECT_PROFILE by Apple’s online authorization service? Specifically: What causes online-auth-agent to return REJECT_PROFILE for a newly created provisioning profile? Can an Apple Developer team/account get into a state where newly generated Development/Ad Hoc profiles are rejected by device-side online authorization? Is there any additional server-side reset or validation Apple Developer Support can perform for Team ID 26K9NDX728? Is error -402620392 associated with a specific provisioning/profile authorization condition? Is there anything else I should inspect in the .mobileprovision file or code signature to determine exactly why Apple is rejecting it? Since I can reproduce this with both Xcode and EAS, is there any known issue affecting Ad Hoc/Development profile authorization rather than the build tooling itself? At this point I’m reluctant to keep generating new certificates and provisioning profiles because I’ve already done a complete signing reset and the newly generated profiles are still being rejected. Any guidance on what REJECT_PROFILE means internally, or what Apple Support should check on the Developer account/team, would be greatly appreciated.

I'm using Dynamic Font throughout my entire app yet the audits in Accessibility Inspector will give me a ton of "Dynamic Type font sizes are unsupported: User will not be able to change the font size of this SwiftUI.AccessibilityNode" warnings. This is incorrect because users are able to change the font size. I can even move to the inspector panel and adjust the font and see it all change right within the Accessibility Inspector. I assume this is a bug since I can change the font but I was also wondering if there's some special thing I'm missing that could prevent these warnings from appearing especially when management runs audits to look for deficiencies.

I'm trying to download the iOS 26.2 simulator, but it fails both in Xcode and via the command line. When I run: xcodebuild -downloadPlatform iOS -buildVersion 26.2 -exportPath ~/Downloads It returns: iOS 26.2 is not available for download. I would like to know: Why iOS 26.2 simulator cannot be downloaded at the moment. Whether iOS 26.2 simulator is still available, or if it has been removed or replaced. How to properly get and install the iOS 26.2 simulator. Any official explanation or solution would be greatly appreciated. Thank you!

Feedback Assistant report: FB25173765. I am investigating an iOS Simulator runtime verification failure on an Apple M1 Mac: macOS 27.0.1 (26A434) Xcode 27.1 RC (27A9275) CoreSimulator 1174.9.2 iOS 27.1 RC Simulator runtime, arm64, build 24A94232 The official download/export command completed successfully: xcodebuild -downloadPlatform iOS -exportPath <export-directory> -buildVersion 27.1 -architectureVariant arm64 It registered the runtime and produced a complete .exportedBundle, including ExportedMetadata.plist, BuildManifest.plist and the Cryptex support files. Xcode's required components are installed, and xcodebuild -checkFirstLaunchStatus returns 0. Updating macOS from 27.0 to 27.0.1 did not resolve the verification failure. xcrun simctl runtime list -j reports a Ready “Patchable Cryptex Disk Image” with signatureState Unknown. Running: xcrun simctl runtime verify <runtime-image-identifier> returns exit code 1 with: Signature verification failed: (-67054 a sealed resource is missing or invalid The registered iPhone Duo simulator has not been booted. No security protections, signing settings or quarantine attributes have been changed, and the existing runtime has not been forcibly removed. Xcode 26.4 release notes, issue 166834291, document secure import of the complete .exportedBundle with xcodebuild -importPlatform. I have not yet run that separate import. Is reimporting the complete bundle a supported recovery for this failure? Does the importer reuse an already registered identical build, and what additional or temporary internal disk space should be reserved? If a different recovery is appropriate, could Apple provide a supported procedure that retains signature and Cryptex validation? Also, is simctl runtime verify the appropriate validation for this runtime format? I have seen community reports involving the inner DMG, but have not assumed those are a confirmed fix or that their validation is equivalent. I would appreciate an official recommendation before proceeding.

I am unable to build to my Series 12 which is on watchOS 27.2 beta 2, I have macOS 27.2 beta 2 and Xcode 27.2 beta 2 but when I open up Device Hub, and click on my watch, it says Tunnel State("Connecting" then "Disconnected") and won't ever connect. the app im building is watchOS only and so iPhone is incompatible and I've tried restarting every device but nothing works.

When working with an Objective-C project in Xcode 26.5, I'm unable to establish outlet and action connections by dragging between XIB files and the corresponding .h header files. This drag-and-drop connection works perfectly after switching to Xcode 26.3.0. In addition, under Xcode 26.5, drag-and-drop linking works normally for projects using Swift files together with XIB files. The issue only occurs with Objective-C .h files and XIB files.

I've never had anything but trouble with xcappdata, but I got what I wanted working in the previous xcode version, I could specify the xcappdata in my testplan and it would work on the simulators. Now, on XCode 27, the xcappdata doesn't load. I look in the xcode 27 release notes and see there is indeed an issue with xcappdata, and a workaround. Workaround: To make a .xcappdata bundle for use in Xcode’s Run scheme action do the following. Add .xcappdata to the folder created by Device Hub when downloading app data containers. Inside that folder make a new folder named AppData. Move the other content in that folder into AppData. For example, com.example.MyApp/{Documents,Library,tmp} becomes: com.example.MyApp.xcappdata/AppData/{Documents,Library,tmp} This is completely unhelpful. When am I downloading app data containers? What folder is created by Device Hub? Where is it? How does this apply to my testplan? What if I have multiple xcappdata bundles for different test plans? It looks to me like this workaround would be part of a script where at some magic moment I inject my app data into a simulator. Which might not be too bad So if I wanted to build this script it I imagine it looks like create a simulator install the app on the simulator find the folder related to the simulator copy in my xcappdata? Then I can run my tests?

Hello. I have just updated to Xcode 27 to support this version, however... my app is a navigation app with CarPlay support... The I/O > External Displays option through the Simulator helps a lot when testing it, but I’ve noticed it is now gone Why? Who thought this was a good idea? Some of us support apps that are beyond a simple ToDo app So now I have to go back to the previous version of Xcode, or what?

How do we get distribution available on Apple HomeView is this iPhone or iPad in Supported Destinations? Thank you.

I’m sharing my experience with an Apple Watch Ultra 2 and Xcode 27.0 in case it helps someone troubleshooting a similar problem. Developer Mode would switch on, restart the Watch, and ask me to confirm “Turn On.” Even after that confirmation, it would revert to off. Xcode detected my iPhone but not the actual Watch, and pairing remained at “Waiting to pair.” The changes that stood out in my case were removing a corporate management/configuration profile that required a complex passcode, changing the Watch to a simple passcode, and putting my Mac, iPhone, and Watch on the same private Wi-Fi network. I also temporarily disabled VPN, restarted both the iPhone and Watch, and enabled Developer Mode again. After these changes, the connection succeeded. I changed several things together, so I can’t identify which change was responsible or claim this is a universal fix. This confirms the connection in my case; installing and running an app on the Watch is still being verified. If your device is managed, consult your organization’s IT team before changing profiles or security settings. This is a report of what happened on my setup, not a recommendation to weaken passcodes or bypass organizational policy.