On November 14, 2026, “Sign in with Apple” started failing on the Claude iOS app — mainly for new accounts. No error code is published; the button simply fails. Anthropic opened an incident at 07:11 UTC and is still investigating. The fix is simple: sign in with Google or email instead.
Quick Fix Summary
- Problem: On November 14, 2026, “Sign in with Apple” started failing on the Claude iOS app — mainly for new accounts. No error code is published; the button simply fails.
- Fix: None user-side. Anthropic opened an incident at 07:11 UTC on November 14 and is still investigating. Sign in with Google or email instead — that path works.
- What happened: Anthropic status incident “Sign in with Apple” on the Claude iOS app — opened 07:11 UTC Nov 14, still open as of Nov 14. No cause published. claude.ai also showed Degraded Performance at the same time.
Technical Root Cause
| Error Code | Affected Version | Root Cause | Current Status |
|---|---|---|---|
| No error code — “Sign in with Apple” fails on the Claude iOS app | Claude iOS app, mainly new accounts signing up or signing in with Apple; claude.ai also Degraded Performance | Not published by Anthropic | Still open as of Nov 14, 2026 — investigating since 07:11 UTC |
Step-by-Step: What to Do When Apple Sign-In Fails on Claude iOS
Step 1 — Check Anthropic’s Status Page First
Open https://status.claude.com and look for the Sign in with Apple incident. If it is open, the failure is Anthropic’s side — nothing on your phone is causing it. This is the same first move as our Fix: ChatGPT Work Mode HTTP 500 Error — when the vendor’s own status page shows an incident, stop troubleshooting your own device.
Step 2 — Sign In With Google Instead
On the Claude iOS sign-in screen, choose Continue with Google instead of Apple. If your Claude account uses the same email as your Google account, you land in the same account. This is the fastest way back in while Apple sign-in is broken.
Step 3 — Or Sign In With Email
If you would rather not use Google, choose the email option and sign in with your email address and password (or the emailed sign-in link). It is the same account — only the sign-in method changes.
Step 4 — Do Not Keep Retrying Apple Sign-In, and Do Not Reinstall
Repeated Apple sign-in attempts do not help while Anthropic is still investigating, and reinstalling the app changes nothing — the failure is in Anthropic’s Apple sign-in path, not in the app on your phone. Save the reinstall for a problem that is actually local, like the sign-in failure we covered in Fix: Claude Code Failed to Refresh OAuth Token — that one is local, this one is not.
Step 5 — Retry Apple Sign-In Only After Resolution
After the status page marks the incident resolved, try Sign in with Apple once. If it still fails after resolution, that is a new problem — check that your Apple ID is signed in on the device and try the Google or email path again before digging further.
Codex on the same iPhone app hit a different bug the same week: the Codex screen shows ‘No tasks yet’ even though your sessions are still there. See Fix: iOS Codex Shows ‘No Tasks Yet’ Bug.
FAQ
Is Sign in with Apple broken for everyone on Claude?
No. Anthropic says the issue mainly affects new accounts signing in on the Claude iOS app. Existing users already signed in are not hit, and claude.ai sign-in with other methods still works.
What should I do instead of Sign in with Apple?
Sign up or sign in with Google, or with email. Do not keep retrying Apple sign-in — repeated attempts do not help while Anthropic is still investigating.
When will Apple sign-in work again?
No time has been given. The incident opened November 14 at 07:11 UTC and is still under investigation. Check status.claude.com — the incident will be marked resolved there first.
Sources: Anthropic status page (status.claude.com), November 14, 2026; AI Parabellum Claude status tracker, November 14, 2026.
Verified by DebugRadar Engineering — Tested on Production Environments
DebugRadar’s engineering team tracks this issue against the vendor’s official status page and reproduces the reported failure before publishing. If the vendor resolves it, we update the guide — check the status links above for the latest state.