Forumics logo Forumics
Issue 01

Back to issue

All Claude Code known issues

CLAIM C163 Supported 2026-11-19

GitHub issue #105770 in anthropics/claude-code, opened 2026-10-28 by BennyWaitWhat, records a report that Android app sign-in fails on a rooted, unlocked-bootloader device: Google Sign-In succeeds and a Play Integrity token is issued, but the server rejects the sign-in with HTTP 400 from POST /auth/verify_google_mobile, and the app shows "Sign-in couldn't be completed because this app couldn't be verified with Google Play"; on the same device Play Integrity reports BASIC only, with DEVICE and STRONG failing; the report affects both the main Claude Android app and the Claude Duet research-preview app, and was filed for a Pixel 9 Pro on stock Android 17, rooted with Magisk 31.

Verbatim Excerpts from Cited Records
“Android app sign-in fails on a **rooted, unlocked-bootloader** device: Google Sign-In succeeds, a Play Integrity token is issued, but the server rejects the sign-in with **HTTP 400 from `POST /auth/verify_google_mobile`**, and the app shows "Sign-in couldn't be completed because this app couldn't be verified with Google Play."”
— BennyWaitWhat · anthropics/claude-code (issue 105770 opening body, Summary section) · 2026-10-28T18:58:32Z ·GitHub Issue ↗
“On the same device Play Integrity reports **BASIC only** — DEVICE and STRONG fail — which on Android 13+ requires hardware attestation from a locked bootloader.”
— BennyWaitWhat · anthropics/claude-code (issue 105770 opening body, Summary section) · 2026-10-28T18:58:32Z ·GitHub Issue ↗
“This affects both the main Claude Android app and the Claude Duet research-preview app.”
— BennyWaitWhat · anthropics/claude-code (issue 105770 opening body, Summary section) · 2026-10-28T18:58:32Z ·GitHub Issue ↗
“The server then rejects: `POST https://claude.ai/auth/verify_google_mobile` → HTTP 400, immediately after `claudeai.login.attestation.resolved`.”
— BennyWaitWhat · anthropics/claude-code (issue 105770 opening body, Actual section) · 2026-10-28T18:58:32Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 17 comments were read. The author (2026-10-28) added a cleaner email/magic-link test on the same device. TateWalker (2026-11-01) and resocketer (2026-11-03) reported the same class of failure on GrapheneOS, including artifacts blocked after the Nov 1 update; roosemberth (2026-11-10) reported email magic-link login is gated on the same check, with /auth/verify_magic_link returning 403; zroug (2026-11-05), rbqbjyur (2026-11-05) and knowledgedelta (2026-11-09) confirmed the sign-in failure on LineageOS, CalyxOS and emulators, with rbqbjyur noting the issue had been tagged invalid and questioning whether it belonged in the Claude Code repo. norby777 (2026-11-14) reported sign-in works once all three Play Integrity verdicts pass, and Marabunta159 (2026-11-14) shared a Play Integrity fix guide. No maintainer fix merged and no retraction of the original report appear in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #105770 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.