Skip to content

Build failed #6

Closed
Closed

Description

@saikee2009

What happened

Build using Xcode, but failed, because I can't use the developer's Team, switch to my Team also doesn't work because it need to change the bundle identifier, I changed and build. Move the app to /Application but "Activate" had problem with extensions.

Repro steps

Expected

Actual

Environment

  • macOS version: 15.7.7
  • Xcode version: 26.3
  • iOS Simulator version / device: N/A
  • SimulatorCamera version: db69036
  • Source used (test pattern / webcam / video file): N/A

Logs / screenshots

os_log output
(paste)
Image

Activity

  1. slowbrewedmacchiato commented on Sep 18, 2026

    @slowbrewedmacchiato

    Hit the exact same wall (macOS 26, Xcode 27), and dug into why "Activate" fails. It's not the bundle — it's sysextd policy.

    What I did: changed the bundle IDs/team to my own (com.dautov.* can't be registered to another team), built, copied to /Applications. The extension is present at Contents/Library/SystemExtensions/, CFBundleIdentifier matches what ExtensionController requests, and codesign --verify --deep --strict passes.

    What sysextd says (log show --predicate 'process == "sysextd"'):

    sysextd: attempting to realize extension with identifier <team-prefixed>.SimulatorCamera.Extension
    sysextd: no policy, cannot allow apps outside /Applications
    sysextd: Failing to realize ... as the app requesting activation isn't in the /Applications folder and developer/groundhog mode isn't on
    

    The app was in /Applications (confirmed via ps and LaunchServices). "No policy" appears to mean no Gatekeeper/notarization policy for the app — so a plain Apple Development-signed build isn't eligible, and the fallback requires systemextensionsctl developer on, which needs SIP disabled.

    Ruled out: Debug vs Release, get-task-allow (rebuilt with CODE_SIGN_INJECT_BASE_ENTITLEMENTS=NO, still fails), stale LaunchServices registrations pointing at DerivedData.

    So as far as I can tell, building from source with a normal dev cert can't activate the extension on a SIP-enabled Mac. Only a Developer ID + notarized build (what build-release.sh produces) will. A published notarized DMG / cask would fix this for everyone hitting it.

    One small thing that would help self-builders: ExtensionController.swift hardcodes com.dautov.SimulatorCamera.Extension; Bundle.main.bundleIdentifier! + ".Extension" works with any prefix.

  2. dautovri commented on Oct 21, 2026

    @dautovri
    Owner

    Thanks @slowbrewedmacchiato — your sysextd analysis was right. The first Developer ID–signed, notarized build is now published: v1.1.0. Download the DMG, drag the app to /Applications and click Activate; no SIP changes needed. The extension bundle ID is already derived from the app's bundle ID, so self-builders can use their own prefix (the smoke test no longer hardcodes com.dautov either, #12). Building from source with a plain dev cert still can't activate on a SIP-enabled Mac, as documented in the README. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions