Getting too much undiagnosable errors - Flutter Sentry in Web

[NicolasDionB]

We recently set-up Sentry in our project and now that it's in production and used by thousands of people we get a lot of errors and some are not quite useful. By that I mean that we get errors coming from the Flutter SDK or some obscure package. That is fine but the stack given for the error is deep and also sometimes minified and so, really hard (if possible!) to diagnose and fix. Such an example is:

When we have errors coming from our code, the stack is mostly fine but outside of that scope, it's minified and we also have a warning at the top saying there are some "Missing Sources Context", like this:

We upload the sources using sentry_dart_plugin, with the following config:

sentry:
  upload_debug_symbols: true
  upload_source_maps: true
  upload_sources: false
  project: live_app
  org: svi-esolutions
  wait_for_processing: false
  log_level: error
  commits: auto
  ignore_missing: true

Finally in my SentryFlutter init, I put the following options:

options.captureFailedRequests = false;
options.enableNativeCrashHandling = false;
options.enableTracing = false;

So on this I have a few questions:

1. How can I fix the Missing Sources Context warning and get all the stacks properly (not minified)
2. Is there a way to disable error catching at this level? Meaning that I want to get errors coming from my code and not be spammed with errors that are too deep. Getting such error is useless if I don't have the source of the problem in my app...
3. Is there a way to influence or set a better title for the exception (instead of "minified:a34" for this example).

Any input on this would be great! Thanks

[buenaflor]

1. this thread might be helpful. Do you also use github actions to upload source maps?
2. I'll have to take a look into that, do you know how this can be reproduced?
3. Symbolicating the title is tracked here Since this is not a trivial matter it requires more investigation from our side

[buenaflor]

Would you mind creating an issue for 2.

[NicolasDionB]

Sure. Would that be a Feature Request or a Bug Report?

[buenaflor]

You can put it as feature request

[NicolasDionB]

Done, I created issue #1751!

[buenaflor]

For 1. please see my comment here. Also read about the source context issue here