Open
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
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.
Summary
com.steipete.CodexBarandcom.steipete.codexbar.cachesecurity delete-generic-passwordoutput in the rebuild logWhy
./Scripts/compile_and_run.shwas only clearing the legacy keychain service.The current runtime cache under
com.steipete.codexbar.cachewas left behind, so a fresh ad-hoc-signed build could still run into stale ACLs and prompt again.This change is limited to CodexBar-owned keychain entries.
Third-party items such as
Claude Code-credentialsstill need stable signing if you want macOS to keep theAlways Allowgrant across rebuilds.Validation
./Scripts/lint.sh lintbash -n Scripts/compile_and_run.sh./Scripts/compile_and_run.sh --testreaches the updated keychain-clearing path, then stops because this environment has Swift 6.0.0 while the package requires Swift tools 6.2Platform check
The app target in this repo is macOS-only, and the keychain cache path is guarded behind
#if os(macOS).I did not find the same issue in the non-macOS code paths in this package.