“xcode github”

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'm submitting a native macOS app (Swift/SwiftUI, arm64) that includes Sparkle.framework for auto-updates. All binaries are signed with a Developer ID Application certificate using --options runtime and --timestamp. I've submitted 12+ times over the past two days, both from local notarytool submit and from GitHub Actions CI. Every submission uploads successfully and returns a valid submission ID, but then stays at In Progress indefinitely — none have resolved to Accepted or Invalid. Two early submissions did eventually come back Invalid — Apple's rejection log showed the Sparkle nested binaries had ad-hoc signatures (they were being signed as individual Mach-O files instead of bundle directories). I fixed this with proper inside-out bundle signing. Since the fix, local codesign --verify --deep --strict passes cleanly, but all ~10 subsequent submissions remain stuck at In Progress. 9UT54V24XG Would appreciate any guidance, or if someone from the notary team could check our queue. Happy to provide spec

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

Hello, I am trying to upload a watchOS standalone app to App Store Connect using Xcode 26.3, but Organizer does not show the “App Store Connect” upload option. It only displays: • Release Testing (Ad Hoc) • Enterprise • Debugging Project setup • Target type: watchOS App (standalone, not companion) • PRODUCT_TYPE = com.apple.product-type.application • PRODUCT_BUNDLE_PACKAGE_TYPE = APPL • WRAPPER_EXTENSION = app • SUPPORTED_PLATFORMS = watchos watchsimulator • Archive configuration: Release • Base SDK: watchOS The app does not depend on iOS. Bundle ID Originally: com.example.app.watchkitapp Recreated as: com.example.app HealthKit capability enabled in: • Developer Portal • Xcode (Signing & Capabilities) Signing • Apple Distribution certificate active • App Store provisioning profile created • Manual signing configured for Release (Apple Distribution + App Store profile) • Also tested Automatic signing • Deleted old Ad Hoc profiles • Cleared Derived Data and regenerated archive App Store Co

Since macOS 26.4 Beta 1, virtual HID devices created via DriverKit can no longer intercept key events from the built-in MacBook keyboard. External keyboards still work. This is confirmed and tracked here: https://github.com/pqrs-org/Karabiner-Elements/issues/4402 One possible lead (from LLM-assisted analysis of Apple's open-source IOHIDFamily code and cross-referencing community reports): macOS 26.4 Beta may have introduced or modified a security policy referred to as com.apple.iohid.protectedDeviceAccess, which could block IOHIDDeviceOpen for the Apple Internal Keyboard connected via SPI transport (AppleHIDTransportHIDDevice). This appears related to a GamePolicy check in IOHIDDeviceClass.m that gates whether processes can open HID devices. This has not been independently verified and may or may not be the root cause. This has far-reaching consequences. Karabiner-Elements alone has over 21,000 GitHub stars and is used by hundreds of thousands of macOS users for keyboard customization, accessibility

I have made an app using Xcode 26.3 Release Candidate 2 for my Apple Watch that runs successfully on the simulator. Xcode comes with the IoS 26.2 and WatchOS SDK 26.2. However, when I do try to connect to my device that have IoS 26.3 and watchOS 26.3, I see a succesful connection to my iPhone but I see the the world symbol and wheel keeps trying to connect on my Apple Watch. I also tried Xcode 26.4 beta 2 with no luck. I reviewed the WatchOS Release Notes: The watchOS 26.2 SDK provides support to develop watchOS apps for Apple Watch devices running watchOS 26.3. The SDK comes bundled with Xcode 26.2, available from the Mac App Store. I also tried Xcode 26.2 but no luck. Any suggestions?