Skip to content

[bug] iOS export options computed from the pbxproj miss provisioningProfiles even when manual signing settings are present #15741

Description

@johncarmack1984

Describe the bug

tauri ios build reads CODE_SIGN_STYLE / CODE_SIGN_IDENTITY / PROVISIONING_PROFILE_SPECIFIER back out of the pbxproj to build its export options. With those settings present and correct inside the target's buildSettings (quoted values containing spaces), the parser does not pick them up: the archive builds and signs, then -exportArchive fails with "requires a provisioning profile" because the computed plist carries no provisioningProfiles map. Possibly related to #14462 (the write side of the same helper).

Reproduction

Manual signing settings in the target's buildSettings of an xcodegen-generated project:

CODE_SIGN_IDENTITY = "Apple Distribution: Name (TEAM)";
CODE_SIGN_STYLE = Manual;
PROVISIONING_PROFILE_SPECIFIER = "Profile Name With Spaces";

xcodebuild -showBuildSettings resolves all three and the archive signs. The export then fails: error: exportArchive ... requires a provisioning profile.

Workaround

Providing gen/apple/ExportOptions.plist with signingStyle / teamID / signingCertificate / provisioningProfiles works: the CLI merges it with the computed options.

Platform and versions

tauri-cli 2.11.4 (pbxproj helper unchanged on dev apart from a loop refactor), macOS, Xcode 26.

Metadata

Metadata

Assignees

No one assigned

    Labels

    platform: iOSscope: cliThe tauri-cli rust crate and @tauri-apps/cli npm packagestatus: needs triageThis issue needs to triage, applied to new issuestype: bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions