Quite confusing log message

[lforst]

WARN 2024-09-02 14:41:35.566111677 +00:00 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 this URL.

I am getting this in our Changelog Vercel logs. https://vercel.com/sentry/changelog/DT2tEb1huCLLTUm7DzDaWawhZHzi#L159

IMO, if the manually provided URL, and the URL in the auth token are matching, we should not print this message.

cc @szokeasaurusrex

[szokeasaurusrex]

strange – I thought I was only printing this when the two URLs are different, but I will double check

[szokeasaurusrex]

Okay, looks like in one of the places we emit this message we check whether the URLs are different, but in the other spot, we don't:

sentry-cli/src/config.rs

Lines 74 to 83 in 288382f

	let url = if token_url.is_empty() {
	default_url
	} else {
	if !default_url.is_empty() {
	log::warn!(
	"Using {token_url} (embedded in token) rather than manually-configured URL {default_url}. \
	To use {default_url}, please provide an auth token for this URL."
	);
	}
	token_url.into()

Should be a pretty simple fix to add this check, thanks for raising @lforst!

[dmadridy]

Hey, just got this message as well when configuring Sentry. Let me know when its solved. Thanks!

[szokeasaurusrex]

@dmadridy hopefully we will get a fix out this week!

[szokeasaurusrex]

@dmadridy @lforst, the fix has been released in Sentry CLI v2.35.0.

[absolutegravitas]

yeesh... What is the actual patch and what does this mean? I have a repo https://github.com/midday-ai/v1 whose deployment to vercel fails because of this unnecessarily confusing message . Upgrading packages for that repo doesnt fix the issue (it's got @sentry/nextjs package).

• do i remove https prefix?
• do i provide auth token again?
• do i remove the https suffix towards the end?

yeesh

[lforst]

@absolutegravitas The log message is confusing but it should not fail your build. You can basically ignore it.

[vonox7]

@szokeasaurusrex I'm using sentry-cli 2.39.1, however I still get the warning when calling sentry-cli --url https://example.org/ sourcemaps upload --org example --project example-project ./dist/example-project:

WARN 2024-12-12 12:57:54.724962 +01:00 Using https://example.org (embedded in token) rather than manually-configured URL https://example.org/. To use https://example.org/, please provide an auth token for this URL.

Note the missing trailing slash in the first url (embedded in token): I created the token via https://example.org/settings/arivo/auth-tokens/new-token/. However, when adding the sentry-cli to my Angular project with npx @sentry/wizard@latest -i sourcemaps (version 3.36.0) the wizard added the following line to the package.json, which contains the trailing slash on the url:

"sentry:sourcemaps": "sentry-cli sourcemaps inject --org example --project example-project ./dist/example-project && sentry-cli --url https://example.org/ sourcemaps upload --org example --project og-frontend-cx ./dist/example-project".

So the workaround is to remove in package.json the trailing slash from the url:
https://example.org/ --> https://example.org.

[szokeasaurusrex]

@vonox7 this seems to be a bug/unintended behavior in the Sentry Wizard. If you are providing an auth token which embeds a URL, the Sentry Wizard should preferably avoid specifying any URL in the package.json, since Sentry CLI always will just use the URL embedded in the token.

I will raise this with the correct team

---

Update: discussed with the team. The behavior will likely stay the same in the Sentry Wizard for now due to backwards-compatibility concerns, but we can improve the logic for comparing the URLs in the Sentry CLI. In the meantime, you can safely ignore this warning.