recordDroppedEvent is not a function
See original GitHub issueIs 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?
SDK Version
7.6.0
Framework Version
@sentry/electron 3.0.7
Link to Sentry event
https://sentry.io/share/issue/25be96dd489041a4869bc487620e9d73/
Steps to Reproduce
Unfortunately we don’t have a clear way to reproduce it, but it seems to happen randomly at the time we span.finish()
when making custom transactions and spans for performance.
Random guess, but do you think it could happen if we create multiple Transaction in parallel?
Expected Result
no crash should happen.
Actual Result
some error are getting thrown on some .finish() cases.
Issue Analytics
- State:
- Created a year ago
- Comments:18 (7 by maintainers)
Top Results From Across the Web
e.captureSession is not a function #3278 - GitHub
I upgraded my React codebase from Sentry 5.26.0 to 6.2.0 and everything fails with this error: e.captureSession is not a function. Reverting ...
Read more >recordDroppedEvent is not a function - PullAnswer
It seems to me, you're using v3 of the electron SDK but v7 of the browser JS SDK. This isn't supposed to work...
Read more >recordDroppedEvent is not a function - getsentry/sentry ...
recordDroppedEvent is not a function. getsentry/sentry-javascript. Issue. Is there an existing issue for this?
Read more >react native - TypeError: r(d[2]) is not a function. (In 'r(d[2])(this ...
I am converting my react-native app to a mono-repo using yarn workspaces. After moving the logic code into shared packages, I am able...
Read more >@sentry/types@7.27.0 - jsDocs.io
This is an internal function to setup all integrations that should run on the client ... If omitted, the SDK will not send...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was able to fix my issue by downgrading to @sentry/nextjs: 6.19.2 and @sentry/tracing: 6.19.2 just like @gre did. There must be some issue with @sentry 7+ for next.js.
Thank you again!
It could also be the Vercel runtime environment. It is odd that the issue is never thrown in local development, even when running a build. It only occurs in a Vercel deployment.
I will continue to look into it. Thank you for your help!