event submission rejected with_reason: ProjectId

[ozgurhanurek]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/react

SDK Version

7.13.0

Framework Version

7.13.0

Link to Sentry event

No response

Steps to Reproduce

We've been using Sentry for a while but didn't really utilize it for our React frontend. Now that I'm taking a closer look at it, I'm seeing some issues.

1. I'm setting up Sentry on my local server (create-react-app with react-app-rewired) according to the guide at https://docs.sentry.io/platforms/javascript/guides/react/
2. I'm trying to throw some errors by either defining a button onClick such as the one below, or directly throwing an error in the React component.

<button
  type="button"
  onClick={() => {
    throw new Error('CUSTOM SENTRY ERROR');
  }}
>
  Throw error
</button>

3. I've failed to reliably send errors to Sentry. I also tried it by first creating another project within my team and then by creating a new project on a new trial account.
4. As far as I can see, this is not isolated to my local server and we are seeing the same problem on production.

Expected Result

To observe the errors I'm throwing on Sentry issues.

Actual Result

Most of the time Sentry request are failing with code 403 with the error message event submission rejected with_reason: ProjectId which means I don't see the errors on Sentry issues. There are times when the error succeeds which returns an id value:

[souredoutlook]

Hey @ozgurhanurek - this typically means your DSN is set incorrectly.

The Sentry DSN conforms the the format below:

{PROTOCOL}://{PUBLIC_KEY}:{SECRET_KEY}@{HOST}{PATH}/{PROJECT_ID}

If you're using the SAAS version of Sentry this will typically be https://{PUBLIC_KEY}@o{ORG_ID}.ingest.sentry.io/{PROJECT_ID}. If the public key, organization ID, or project ID are not correct, you'll see this error.

The quickest way to check if you're using the correct key is to go to the project settings page for the relevant project:

https://sentry.io/settings/{org_slug}/projects/{project_slug}/keys/

[ozgurhanurek]

Hey @souredoutlook, thanks a lot for your quick response. I did more digging after this and eventually found out that GTM was injecting another Sentry initialization script tag with a different DSN which was causing the errors to go somewhere else entirely. Appreciate your help!