Skip to content

Conversation

jkmassel
Copy link
Contributor

Adds code signing to the release and debug XCFrameworks. This allows consumer projects to ensure the binary dependency hasn't been tampered with.

@jkmassel jkmassel force-pushed the add/xcframework-code-signing branch 2 times, most recently from e70ef6e to 3a46021 Compare October 16, 2025 03:14
@jkmassel jkmassel force-pushed the add/xcframework-code-signing branch from 3a46021 to 2d78421 Compare October 16, 2025 03:32
team_id: APPLE_TEAM_ID,
api_key: app_store_connect_api_key,
type: 'development',
certificate_id: 'Apple Development: Created via API (886NX39KP6)',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about using the "Apple Distribution" one instead? I feel like it's appropriate to use binaries that are signed with "Apple Distribution" on all builds, but "Apple Development" builds may not be suitable for release builds.


# Code Signing
APPLE_TEAM_ID = 'PZYM8XX95Q'
APPLE_BUNDLE_IDENTIFIER = 'com.automattic.hostmgr'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I understand it correctly, this bundle id is only for fastlane to download the certificates and things. If that's the case, can we move it into the set_up_signing lane, to avoid the potential confusion that com.automattic.hostmgr is the "bundle id" of the wordpress-rs xcframework?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants