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 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?

Just download 27.1 and Device Hub 27.1 and unable to locate the iPhone Duo simulator. Please help what are the steps to get this? I have both Xcode 27 and Xcode 27.1 installed. Launched 27.1 does not have Duo sim and all test devices in providing incompatible... What are the exact steps for testing an existing app with compatibility with 27.1 iPhone Duo? Thank you.

Is there a way to simulate Display Zoom settings under the Appearance tab in Settings on a device simulator? I can only find this setting in my real device.

My app uses a notification service extension and a notification content extension, both of which are considerably complex and result in a few different dozen combinations of notification with various layouts and content. Regression testing of all the multitude of combinations of notifications is time consuming. Is there any tools available that can utilized to create a test harness? I was thinking something like the test harness sends a series of pushes and each resulting notification gets checked. Is XCUITest capable of verifying the content/layout of notifications? If so how could XCUITest be incorporated with a test harness that is driving things and sending the pushes etc.

Hi everyone, I’m currently preparing the launch of Ritmo, a new iOS dating app for active people, and I’m looking for a few developers/users who would be willing to test it on TestFlight. I’d especially appreciate feedback on: Onboarding Profile discovery Likes and matching Messaging Notifications Overall UX and bugs It should only take around 10 minutes. TestFlight: https://testflight.apple.com/join/qGbXXeph Any feedback would be really helpful. Thanks!

Hello, Running unit tests fires up the simulator, which is so slow. Is it feasible, for an iOS project, to move all logic into an external package (no UI imports)? That feels like a sledgehammer just to make tests run a bit quicker. And all the extra potential mistakes of running one app across two projects. Are there other/better approaches to test logic only in an Xcode iOS project? Buy a bigger laptop? :) Thanks

We are experiencing an issue with our TestFlight build The build was successfully uploaded to App Store Connect and is available for internal testing. Our internal testers can see the build in TestFlight, but when they attempt to install it, they receive the following error: "Could not install Game. The requested app is not available or doesn't exist." This issue occurs for all internal testers. The build upload completed successfully, and the build is assigned to the internal testing group. We are unable to determine the cause of this issue. Could you please help us identify whether there is any missing configuration or any other requirement that could be preventing the app from being installed?

Hi everyone, I'm trying to run a Mac app UI tests on our CI servers (Mac minis). The servers are logged in, but the lock screen is active (aka, the active process is the com.apple.loginwindow). UI tests end up failing with: Failed to activate application (current state: Running Background) Is there any way to run Mac UI tests on a server like this without having to disable the lock screen? Our admins will likely not accept that solution, and I agree with them. Aside from running a full VM just for the UI tests, I can't find any solution. Thank you, Miguel Arroz

My iPhone SE (3rd generation) keeps developing a dead zone on the left side of the screen. It resolves itself after a restart, but comes back shortly after. It started when I was beta testing iOS 27 Beta 1, but I've since tried both updating to Beta 2, and downgrading back down to iOS 26. The problem persisted on all three versions. I currently have it on iOS 26.5.2. I did have a screen protector on it, but it started a while after I had it applied. I tried removing it to see if that would fix it, but it didn't. I have a case on the phone and have never dropped it or spilled anything on it, I am very careful with it, and only got it a couple weeks ago. Has anyone else had this problem? How can I fix it? Any help is appreciated!

I know that using a mouse to control an iPhone simulator on macOS allows me to swipe down from the top right corner to open the Control Center, but why can't I swipe down from the top left corner to open the Notification Center? Am I doing something wrong, or does iOS disable mouse access to the Notification Center on macOS? Also, it seems that you can't use a mouse or gestures to open the Notification Center or Control Center in iPhone Mirroring at all. I saw that Accessibility has a feature to open the Notification Center or Control Center with the keyboard, but it doesn't work in my tests on macOS. I have an application feature that needs to check the effect of the media playback cards in the Notification Center, but I can't check it at all. Every time I compile to a real device and test manually. Is there any way to reliably trigger the Notification Center and Control Center on macOS? Otherwise, testing on a real device every time is too cumbersome, and I can't automate the testing at all!

Hello, I would like to suggest adding dedicated keyboard shortcuts or menu commands for opening Notification Center and Control Center in both iOS Simulator and iPhone Mirroring. At the moment, these interfaces generally need to be opened by dragging downward from a specific area at the top of the simulated or mirrored iPhone screen. While this works for normal manual interaction, it is less reliable when using a mouse, especially when the window is resized or when the pointer needs to begin very close to the screen edge. This also creates difficulties for automated UI testing and computer-use agents, such as Codex-based testing workflows. These systems interact with the screen through mouse and keyboard input, so accurately reproducing an edge swipe can be unreliable. A small difference in the starting position may open Spotlight, scroll the current application, move the window, or fail to trigger the system interface entirely. It would be helpful if Apple could provide commands such as: Open Notification Center Open Control Center Dismiss Notification Center or Control Center These commands could be exposed through: Keyboard shortcuts The Simulator “Device” or “Features” menu The iPhone Mirroring toolbar or menu bar Accessibility or UI automation interfaces For example, Simulator already provides menu commands and shortcuts for actions such as pressing the Home button, locking the device, rotating the screen, and triggering other hardware-related interactions. Notification Center and Control Center could be handled in a similar way. This would improve: Manual testing with a mouse and keyboard Automated testing of applications that interact with notifications, media controls, Bluetooth, Focus modes, screen recording, and other system features Accessibility for users who have difficulty performing precise drag gestures Reliability for computer-use and vision-based testing agents Ideally, the commands should behave like genuine system gestures rather than directly changing internal state, so developers can test the complete user-visible interaction. Thank you for considering this feature.

We got the newly issue that our Test devices keeps us asking for the pin code to "Enable UI Automation". Then it works for some hours or days, but after some time it starts again. "Enable UI Automation" is already enabled in "Settings" - "Developer" menu. The devices are located remotely and we can't access them directly, so this is a big issue for us right now. Is there any way to avoid this?

Hey all, I have been suffering from obesity for a long time, and I recently built an agent to help me manage my weight. The results for me have been great, to say the least. I started at 125kg, 180cm 3 months back. After 90 days, I am at 110.7kg only by making micro-adjustments to what I eat and following the AI assistant's guidance. Hence, I made it an app experience and would love it if someone could help me with testing. I can help them test their apps in return

I am getting this error when trying to run my tests: Library not loaded: @rpath/XCTestCore.framework/XCTestCore Referenced from: <498690CD-C914-3EE9-8EC1-C3BA4EF513CA> /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/lib/libXCTestSwiftSupport.dylib Reason: tried: '/Users/<>/Library/Developer/Xcode/DerivedData/Sonnet-bqruszxvmhdevmbxdbnagkvhywae/Build/Products/Test Project-iphonesimulator/XCTestCore.framework/XCTestCore' (no such file) It is only appearing on the DeviceHub. When I run the tests in my xcode 26, with the old Simulator, they run just fine.

Details: I'm looking for clarification on how Guideline 1.4.3 is applied to tobacco related apps. My app, The Leaf Cellar, was rejected under 1.4.3 with the reasoning that its "current concept is not appropriate" because it relates to tobacco. The app is a private inventory manager. It has no store, no purchasing, no vendor or affiliate links, no discovery feed, and no content directed at encouraging or using tobacco. its only function is personal record-keeping (logging inventory you already own, aging dates, humidity readings). A 21+ age gate is enforced on launch. What I'm trying to understand is the consistency of the guideline, because functionally identical apps are currently live on the store and receiving updates (which means apple must approve the submitted updates.) Existing Apps (not being enforced by 1.4.3): "My Humidor – Cigar Journal": [https://apps.apple.com/us/app/my-humidor-cigar-journal/id6639582700] "Humidor Journal Pro": [https://apps.apple.com/us/app/humidor-journal-pro/id6751737114] Questions: Is there a specific feature or distinction that separates an approvable cigar-journal app from one rejected under 1.4.3 as a "concept"? If apps in this category are already approved, what's the correct path to have an inconsistent rejection reviewed beyond the standard Resolution Center reply? I have already submitted to the App Review Board.

Hi all, We can’t install our app from TestFlight. The app is visible in TestFlight for invited internal testers, but tapping Install fails immediately with: “The requested app is not available or doesn’t exist.” --Setup-- Distribution: TestFlight – Internal Testing Internal group created and testers added (invite accepted) Build processing status in App Store Connect: Complete TestFlight build status shows: Ready to Submit / Prepare for Submission Minimum iOS deployment target: iOS 15.0 Version/Build: 1.0.0 (1) What we tried Confirmed tester is signed into TestFlight with the same Apple ID email that was invited Removed/added testers to the internal group and resent invites Reinstalled TestFlight, signed out/in Verified build is assigned to the internal group Set and saved Monetization → Pricing and Availability → App Availability (All Countries/Regions) Question Has anyone resolved this issue? Is there a known TestFlight/App Store Connect stuck state that causes this error even for internal testing? Any recommended steps (new build number, group reset, availability/pricing settings, etc.)? Screenshots available (TestFlight error + App Store Connect build/group view). Thanks.

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.

Hello, I am unable to install my app from TestFlight even though the build appears valid and is in internal beta testing. The build was uploaded successfully to App Store Connect and shows as Testing / Internal Testing. The build metadata looks valid: processingState: VALID internalBuildState: IN_BETA_TESTING qcState: BETA_INTERNAL_TESTING usesNonExemptEncryption: false minOsVersion: 15.0 deviceFamilies: IPHONE supportedArchitectures: arm64 However, TestFlight installation fails, and the App Store Connect API returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta contract is missing for the app. My App Store Connect agreements are all active. I checked Business > Agreements and both Paid Apps Agreement and Free Apps Agreement are Active. Bank accounts, tax forms, and compliance also appear Active. This also happens with a newly created app and a fresh build, so it looks like the TestFlight beta contract may be missing or detached on Apple’s backend. Has anyone seen this before, or is there a way to force App Store Connect to refresh the TestFlight beta contract state?

On https://developer.apple.com/documentation/AppIntentsTesting/testing-your-app-intents-code Apple showcases the following example using AppIntentsTesting to query entities indexed in spotlight. For me, calling .spotlightQuery on any entity definition causes a crash. func testAllEventsIndexed() async throws { let eventDef = definitions.entities["EventEntity"] let allIndexed = try await eventDef .spotlightQuery(nil) XCTAssertGreaterThanOrEqual(allIndexed.count, 3) } Crash: expression unexpectedly raised an error: Failed to obtain the result of the distributed invocation after it was executed. Remote threw executionPermissionDenied(requestBundleID: Is anyone else seeing this crash, or is it just me? Thanks!