Scope data not getting set when calling captureException

[ryan-gray-db]

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/node

SDK Version

7.27.0

Framework Version

7.27.0

Link to Sentry event

https://sentry.io/organizations/dreambound/issues/3823746073/events/bbe20bb968c346fa876f84ba7d0a80a8/?project=5671000

Steps to Reproduce

No scope context, user, tags, etc seems to be getting set, via any method of setting scope (e.g. Sentry.setContext, captureException(error, someScope), etc). When debugging, I can see an exception begin caught inside scope.js where it's trying to spread undefined with [...scope._attachments]

Expected Result

Context, user, tags, etc to be shown in the Sentry error event

Actual Result

No context, user, tags, etc are shown in the Sentry error event

[Lms24]

Hi @ryan-gray-db,

interesting. Could you tell me a little more about your setup? What kind of Node app are you working on? Express? What are the minimal steps to reproduce this error?

I'm also having a hard time understanding the error that seems to be causing this. The only place where we're using the spread operator on scope._attachments is here:

sentry-javascript/packages/core/src/scope.ts

Line 132 in aad38ab

newScope._attachments = [...scope._attachments];

However, to me it seems as if _attachments would always be defined (it seems to be set to an empty array by default).

Could you check that all @sentry/* packages in your node_modules and lock file are up to date and on the exact same version? Perhaps there is some discrepancy that could explain this.

[ryan-gray-db]

Hey, thank you so much for the response!

I spent a while debugging more today, and found that filestack-js is including @sentry/minimal@6.x, which includes @sentry/hub@6.x. I'm thinking that sentry@6 is setting a scope globally that doesn't have _attachments on it, then it's retrieved by my code using sentry@7. So this sounds a little more like filestack-js needs its sentry version updated, but it would be nice if they could be backwards compatible to an extent. Maybe if 7 could "repair" the scope when it's retrieved?

[ryan-gray-db]

For anyone else that comes across this, here's the filestack-js issue:
filestack/filestack-js#482

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀