[Bug] Refuses sandbox tester iCloud sign-in on iOS Simulator

Title

Claude Code won't sign into an Apple sandbox tester account on the iOS Simulator, even with explicit user permission

Summary

When an iOS Simulator asks for the password of an App Store Connect sandbox tester account, Claude Code refuses to type it. That holds when the user grants explicit permission in chat and when the user's memory records standing permission for it. Claude says the rule is a fixed part of its instructions that the user can't override. It treats any OS-level Apple sign-in like a real credential prompt.

Sandbox testers are fake accounts Apple provides for development. They hold no real data, no payment method and no access to production users. Signing one into a simulator is the documented way to test iCloud, CloudKit, StoreKit, in-app purchases and Sign in with Apple.

Steps to reproduce

1. Create a sandbox tester in App Store Connect and sign it into an iOS Simulator once.
2. Later, iOS asks for that account's password again ("Apple Account Verification" alert, or Settings → Apple Account).
3. Ask Claude Code to re-enter the sandbox tester's password so it can finish an end-to-end test of the user's own debug build.
4. Give explicit permission in chat.

Expected

Claude enters the sandbox tester's password and continues the test. It already does this for test credentials on the user's own app at localhost. A simulator running the user's own debug build, signed into a sandbox tester, is the same kind of test environment.

Actual

Claude refuses on every request, even after repeated explicit permission. Each time, the user has to stop and type the password by hand. This happened in the middle of verifying a fix for a live production bug. The behavior has also been inconsistent: the same sign-in was done in earlier sessions.

Impact

• Beyond infuriating that this permission is stopping every single long running task on auto mode.
• Blocks unattended end-to-end testing of any iOS or macOS app that uses iCloud, CloudKit, StoreKit or Sign in with Apple.
• Simulator sandbox sessions expire regularly, so this comes up again and again across every Apple-platform project, not once.

Proposed fix

• Treat an Apple sandbox tester on an iOS or visionOS Simulator, running a build of the user's own project, like any other test credential for the user's own app.
• Or add an opt-in setting or allowlist, for example a list of sandbox tester addresses in settings.json, that the user controls.
• The iOS simulator is not Chrome. Claude seems to enact this non-logical behavior after connecting chrome browser. He even mentions sometimes that it stems from that connection.

Environment

• Claude Code CLI on macOS, auto mode
• Xcode iOS Simulator