Fixes #0: unblock local run with valid signing identity#67
Open
peterw wants to merge 2 commits intofarzaa:mainfrom
Open
Fixes #0: unblock local run with valid signing identity#67peterw wants to merge 2 commits intofarzaa:mainfrom
peterw wants to merge 2 commits intofarzaa:mainfrom
Conversation
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
1 participant
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.
Group chat announcement
Clicky was not launching locally because the project was pinned to a missing Apple team and missing development certificate. I switched the app target signing to use the local Developer ID identity so Run works again.
Customer message
No customer-facing behavior changed. This fix only unblocks local developer launch/build.
QA checklist
Clicky.appfrom DerivedData.4.5) BLAST RADIUS
Low. Signing settings only.
Why this works
Before: target referenced unavailable team
2UDAY4J48Gand expected Mac Development cert.Now: target uses local
Developer ID Applicationidentity with team43ZGN39D84, matching available identity on this machine.Key concepts
macOS app signing in Xcode can fail at Run-time if team/cert pair in project settings does not match installed identities.
Old vs new response
N/A
Prompts used
Restate the issue
Fixed local launch failure caused by stale code-signing team/certificate settings.
UI simplification note
No UI changes.
Live page proof
No production UI route affected; this is Xcode project config only.
safe to ship? what's the worst thing that could happen?
Safe for local dev unblock. Worst case is signing mismatch on another machine that uses a different cert/team and needs local adjustment.