Add Extensions-WatchWidgets App Store provisioning profile#5032
Merged
Conversation
The WatchWidgets extension added in #5027 has no App Store provisioning profile for its bundle id io.robbie.HomeAssistant.watchkitapp.WatchWidgets, so the App-Release archive in the Distribute workflow fails to sign it. CI imports the profiles committed under Configuration/Provisioning (setup_ha_ci -> import_provisioning_profiles), so the newly created "iOS App Store - Extensions-WatchWidgets" profile is added there alongside the rest. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
bgoncal
force-pushed
the
fix/watchwidgets-codesign
branch
from
7bf27d4 to
9fc18f2
Compare
bgoncal
changed the title
Contributor
|
Found 3 unused localization strings in the codebase. Click to see detailsTo remove them, run the |
bgoncal
added a commit
that referenced
this pull request
Jul 10, 2026
…5033) ## Summary Follow-up to #5032. Committing the provisioning profile was necessary but not sufficient: the **Distribute** workflow's `App-Release` archive still fails with the same error ([latest failing run](https://github.com/home-assistant/iOS/actions/runs/29084034712/job/86333386325)): > `Extensions-WatchWidgets has conflicting provisioning settings. Extensions-WatchWidgets is automatically signed, but provisioning profile iOS App Store - Extensions-WatchWidgets has been manually specified.` `Extensions-WatchWidgets` (added in #5027) was created via the Xcode new-target wizard, which hard-coded `CODE_SIGN_STYLE = Automatic` into its Debug **and** Release build configs. Every other shipping target (`App`, `WatchApp`, all `Extensions-*`) leaves `CODE_SIGN_STYLE` unset at the target level and inherits it from the xcconfigs: - `Configuration/HomeAssistant.xcconfig` → `Automatic` for Debug - `Configuration/HomeAssistant.release.xcconfig` → `Manual` for the archive, plus `PROVISIONING_PROFILE_SPECIFIER[sdk=watchos*] = iOS App Store - $(TARGET_NAME)` The target-level `Automatic` overrode the xcconfig's `Manual` while the manual profile specifier was still inherited. xcodebuild rejects that combination at signing-settings resolution — **before** the profile is even used — which is why adding the profile in #5032 didn't clear it. Removing the two lines lets WatchWidgets resolve signing exactly like `WatchApp`: `Manual` + the `iOS App Store - Extensions-WatchWidgets` profile for the release archive, `Automatic` for local Debug builds. ## Changes - Remove target-level `CODE_SIGN_STYLE = Automatic` from `Extensions-WatchWidgets` (Debug + Release). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.