Skip to content

Use any existing asc profile, not only a Keychain one - #181

Merged
sreejithraman merged 1 commit into
mainfrom
fix/asc-repeated-password-prompt
Nov 15, 2026
Merged

sreejithraman merged 1 commit into
mainfrom
fix/asc-repeated-password-prompt

Conversation

@sreejithraman

Copy link
Copy Markdown
Owner

Summary

The app-store-connect skill told agents to prefer a Keychain asc profile. Homebrew builds asc with an ad hoc signature, so each upgrade changes its code hash and the Keychain asks for the password again. A file-backed profile (asc auth login --bypass-keychain) avoids that, but an agent following the old line could log back in to the Keychain and bring the prompts back.

Agents now use whatever working asc profile exists, Keychain or config file, and run asc auth login only when none works.

Evidence

  • python3 scripts/check.py passes.
  • Independent Primary review (GPT-6.1 Sol): no findings.
  • Checked live: with only the file-backed profile, asc apps list works from any folder with no prompt.

Merge Danger

Low. One instruction line; no scripts or host settings change.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sreejithraman
sreejithraman force-pushed the fix/asc-repeated-password-prompt branch from 44f3e7e to 013e8e5 Compare November 15, 2026 06:21
@sreejithraman
sreejithraman merged commit d0f759b into main Nov 15, 2026
3 checks passed
@sreejithraman
sreejithraman deleted the fix/asc-repeated-password-prompt branch November 15, 2026 06:25
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.

1 participant