From 7e09ef392df3f9841d41e17688d434f5d6e1e7bb Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 14 Jul 2026 09:54:04 +0000 Subject: [PATCH] ci: stop overriding SENTRY_AUTH_TOKEN with a literal in eas.json MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit eas.json build-profile `env` values are static strings — they are not shell-expanded — so "SENTRY_AUTH_TOKEN": "$SENTRY_AUTH_TOKEN" passed the literal string "$SENTRY_AUTH_TOKEN" to sentry-cli, which Sentry rejects as an invalid token (HTTP 401). Because a build-profile env value also takes precedence over the EAS-hosted environment variable of the same name, this override silently shadowed the real (rotated) production token, so source-map upload 401'd on both Android and iOS regardless of rotation. Remove the key so the EAS-hosted `production` SENTRY_AUTH_TOKEN is used directly. SENTRY_ALLOW_FAILURE=true stays as a safety net. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_017LWh8sKPgZWEF7JNvFxq3g --- eas.json | 1 - 1 file changed, 1 deletion(-) diff --git a/eas.json b/eas.json index c1c48ace8..c73519058 100644 --- a/eas.json +++ b/eas.json @@ -20,7 +20,6 @@ "disabled": true }, "env": { - "SENTRY_AUTH_TOKEN": "$SENTRY_AUTH_TOKEN", "SENTRY_ALLOW_FAILURE": "true" } }