Ever since we fixed the Sentry integration, we've certainly been seeing exceptions flow through – they're just not very helpful.
Current Behavior
This is what most of them look like:
Possible Solution
Here are a few ideas:
Move to Sentry.captureMessage given that the current objects passed to captureException are clearly not Errors
Remove the Sentry integration entirely (and just let users configure this in their application)
Steps to Reproduce (for bugs)
I can try to come up with an example Sentry event (without sensitive information) if necessary.
Additional Screenshots
Context
Ultimately, we'd like to better understand / diagnose Filestack picker upload-related errors. This includes better fingerprinting in addition to exception context.
Your Environment
Version used: 3.25.0
Browser Name and version: Chrome Version 95.0.4638.69
Operating System and version (desktop or mobile): macOS Version 12.0.1
Expected Behavior
Ever since we fixed the Sentry integration, we've certainly been seeing exceptions flow through – they're just not very helpful.
Current Behavior
This is what most of them look like:
Possible Solution
Here are a few ideas:
Sentry.captureMessagegiven that the current objects passed tocaptureExceptionare clearly notErrorsSteps to Reproduce (for bugs)
I can try to come up with an example Sentry event (without sensitive information) if necessary.
Additional Screenshots
Context
Ultimately, we'd like to better understand / diagnose Filestack picker upload-related errors. This includes better fingerprinting in addition to exception context.
Your Environment