Skip to content

Fix manually-configured URL warning when using org tokens - #3420

Open
Nezz wants to merge 2 commits into
getsentry:masterfrom
Nezz:fix/url-conflict-trailing-slash
Open

Nezz wants to merge 2 commits into
getsentry:masterfrom
Nezz:fix/url-conflict-trailing-slash

Conversation

@Nezz

@Nezz Nezz commented Oct 2, 2026 •

Copy link
Copy Markdown

Description

Org auth tokens (sntrys_) embed the instance URL without a trailing slash (https://sentry.io), while a configured URL often has one (https://sentry.io/). The CLI compares the two as plain strings, so it prints a conflict warning even when both point to the same server:

Using https://sentry.io (embedded in token) rather than manually-configured URL https://sentry.io/. To use https://sentry.io/, please provide an auth token for https://sentry.io/.

This comes up constantly for Expo/React Native users: @sentry/expo-upload-sourcemaps sets SENTRY_URL=https://sentry.io/ by default, so every sourcemap upload with an org token triggers the warning.

The fix is to trim trailing slashes before comparing, so the warning only fires on real conflicts.

Issues

N/A — no tracking issue; happy to open one if preferred.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

Nezz and others added 2 commits October 2, 2026 15:46
Auth tokens with embedded URLs (e.g. sntrys_ org tokens) store the
instance URL without a trailing slash (https://sentry.io), while
manually-configured URLs commonly include one (https://sentry.io/) —
notably the default SENTRY_URL injected by @sentry/expo-upload-sourcemaps.
The literal string comparison flagged these as conflicting and warned
even though both URLs are the same server.

Compare URLs with trailing slashes trimmed so only genuine conflicts warn.

_Written by AI_

Co-authored-by: Cursor <cursoragent@cursor.com>
_Written by AI_

Co-authored-by: Cursor <cursoragent@cursor.com>
@Nezz Nezz changed the title fix: Ignore trailing slashes in URL conflict warning Fix manually-configured URL warning when using org tokens Oct 2, 2026
@Nezz
Nezz marked this pull request as ready for review October 2, 2026 17:35
@Nezz
Nezz requested review from a team and szokeasaurusrex as code owners October 2, 2026 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant