ci: stop overriding SENTRY_AUTH_TOKEN with a literal in eas.json - #2247
Open
MusabShakeel576 wants to merge 1 commit into
Open
ci: stop overriding SENTRY_AUTH_TOKEN with a literal in eas.json#2247MusabShakeel576 wants to merge 1 commit into
MusabShakeel576 wants to merge 1 commit into
Conversation
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 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017LWh8sKPgZWEF7JNvFxq3g
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
eas.json build-profile
envvalues 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
productionSENTRY_AUTH_TOKEN is used directly. SENTRY_ALLOW_FAILURE=true stays as a safety net.Claude-Session: https://claude.ai/code/session_017LWh8sKPgZWEF7JNvFxq3g