These exceptions might be harmless but they are muddying up Sentry and should be caught.

• https://sentry.io/organizations/minds-inc/issues/1384098907
• https://sentry.io/organizations/minds-inc/issues/1177357869
• https://sentry.io/organizations/minds-inc/issues/1384007806
• https://sentry.io/organizations/minds-inc/issues/1384675732
• https://sentry.io/organizations/minds-inc/issues/1384120447
• https://sentry.io/organizations/minds-inc/issues/1384999350
• https://sentry.io/organizations/minds-inc/issues/1384970051
• https://sentry.io/organizations/minds-inc/issues/1383435876

added scoped labels

Useful links:

• https://github.com/getsentry/sentry-javascript/issues/2210
• https://github.com/getsentry/sentry-javascript/issues/424

assigned to @benhayward.ben

added scoped label

added scoped label

unassigned @markeharding

Discussed in meeting just now,

Emi pointed out the error is in a promise in their code, so we cannot catch it.

First step I'm going to look into whether there is a config option to silence the errors. Second step I'm going to post on Playrs Github/Gitlab.

If we still cannot silence the errors, we plan to look into whitelisting in Sentry.