Issues are saved 3 hours in the past

[hyperknot]

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• Provide a link to the affected event from your Sentry account
  https://sentry.io/share/issue/61429f7eeba34cd6993736bfb5ae125c/

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other:

Version:

5.17.0

Description

I have a Create React App, made about 1 year ago, from which if I delete everything and insert only the following:

import * as Sentry from '@sentry/browser'

Sentry.init({
  dsn: '...',
})

Sentry.captureMessage('test')

It creates an issue which is 3 hours in the past. This is visible in the network panel as well, the request is sent with the wrong timestamp.

If I insert the same code to a brand new Create React App, made today, the event will have the correct timestamp.

Since I've removed all code from my app, I have no idea what can trigger this bug in Sentry, to make everything 3 hours in the past. Since migrating everything to a new Create React App is not a simple task, I'd like to try to fix it on the existing build config.

[rhcarvalho]

I have no idea what can trigger this bug in Sentry,

This is most likely related to #2590. The browser reporting time in the past.

@hyperknot what browser are you using?

[hyperknot]

@hyperknot what browser are you using?

Chrome 83 / macOS. What's interesting is that it really depends on the underlying Create React App / Webpack / Babel environment. If I make a new app based on a new CRA environment, it gets the date correctly.

[rhcarvalho]

From the current report alone, this sounds like it would be hard to reproduce.

The event https://sentry.io/share/issue/61429f7eeba34cd6993736bfb5ae125c/ was received 2020-06-17T20:06:18.780Z, a few ms after the timestamp sent from the SDK.

Did you check on your browser's devtools network tab that the time that is being sent in the JSON payload matches the current time? Could you please verify?

Thanks!

[hyperknot]

The issue got multiple events now, here is the first one:

[renchap]

I just noticed the same issue, an error that happened right now (I triggered it) is reported as Sentry as having happened yesterday:

Event is 15deb2ada20347a2b27a24d78aced0de, JS SDK 5.18.0

[AbhiPrasad]

Closing this issue as work was put in with #3356 to fix possible timing issues. If you are still encountering this problem, please re-open the issue. Thanks!