“Xcode”

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 SW

I decided to try out XCode 26.2s new AI abilities but I only get a Your request couldn't be completed. When clicking the details button I get see this error: InferenceError::unspecifiedUnderlyingError::Error(message: Unknown parameter: 'tool_call_outputs'., type: invalid_request_error, code: Optional(unknown_parameter), privacyPassRedemptionResponse: nil, userFacingLocalizedErrorMessage: nil) How do I fix that?

Context: I am building an iOS productivity app using EAS Build. The project has 4 targets: the main app and 3 extensions (ShieldAction, ShieldConfiguration, ActivityMonitorExtension). The Issue: I have officially received approval from Apple for the Family Controls (Distribution) entitlement for my main Bundle ID. However, the build still fails during the Xcode phase. The Errors: Xcode reports that the generated provisioning profiles do not include the com.apple.developer.family-controls entitlement. For example: Provisioning profile *[expo] com.*.** AdHoc 177247892.... doesn't support the Family Controls capability. All 3 extensions are failing with the exact same error. What I've done: Confirmed approval from Apple for com.*.**. Enabled Family Controls and App Groups on the Apple Developer Portal for all 4 Identifiers. Cleared EAS local and remote cache using eas build --clear-cache. Deleted existing profiles on both Expo.dev and Apple Portal to force regeneration. The Question: Even with

Hello Apple Developer Support, I’m developing a virtual camera using the CMIOExtensionDevice / CMIOExtensionStreamSource APIs on macOS. While the virtual camera appears in system settings and apps like Zoom and Google Meet, the video output exhibits the following issues: Jittering frames: The first frame sometimes appears correctly, but subsequent frames flicker or jitter. Solid color fill: Eventually, the camera feed fills entirely with a solid accent color (e.g., blue), rather than the intended video content. Console logs: Repeated messages appear in Console.app: Invalid display 0x00000000 Setup details: The virtual camera is created using CMIOExtensionDevice and CMIOExtensionStream. Video frames are rendered from NSImage/CGImage using CGContext and copied into CVPixelBuffers. Frame delivery is controlled by a DispatchSourceTimer at 60 FPS. macOS version: 26.2 Xcode version: 26.1 Observations: The Invalid display 0x00000000 logs suggest that CGContext drawing or NSImage operations are failing in he

I am using official MCP SDK. According to official guide, Servers MUST provide structured results that conform to this schema. https://modelcontextprotocol.io/specification/draft/server/tools#output-schema I could see output schema defined, but result have no structured content. Current output schema: { name: XcodeListWindows, title: List Windows, description: Lists the current Xcode windows and their workspace information, inputSchema: { type: object, properties: { }, required: [ ], }, outputSchema: { type: object, properties: { message: { description: Description of all open Xcode windows, type: string, }, }, required: [ message, ], }, } Current response: { result: { content: [ { type: text, text: {message:* tabIdentifier: windowtab1, workspacePath: xxxn* tabIdentifier: windowtab2, workspacePath: xxxn}, }, ] } } Expected: { result: { content: [ { type: text, text: {message:* tabIdentifier: windowtab1, workspacePath: xxxn* tabIdentifier: windowtab2, workspacePath: xxxn}, }, ], structuredCon

When I create an archive file and attempt to upload the app using the Distribute App button, the upload fails with the error Automatic signing cannot update bundle identifier.... (The detailed message is below.) When creating an archive file in Xcode, I unchecked Automatically Manage Signing and proceeded with the archive. The message says Font Enumeration, but other apps with the same option enabled upload successfully. Therefore, I believe the Font Enumeration option is not the issue. I tried creating a new provisioning file, but it still doesn't work. I deleted all DerivedData files from my Mac storage, restarted Xcode, and tried again, but it still doesn't work. This keeps happening only for certain targets (specific apps) in Xcode. Does anyone know how to fix this? Xcode is the latest version. Message: Automatic signing cannot update bundle identifier com.xxxxxx.xxxxxx. Automatic signing cannot update your registered bundle identifier to enable Font Enumeration. Update