Often we encounter in Sentry stacktraces like this one https://github.com/flutter/flutter/issues/151834
In the whole stack trace does not appear one of the source files or our app which is probably due to the fact that the error is happening in the Element tree that is created based on our widget definitions but not in our widgets code.
Proposal
It would be incredibly helpful and time-saving if the flutter framework would offer more information about which widget was the source of a crash. If this information would not need to be included in any exception that the framework throws, It would be enough if we could query some post mortem info before we send the error to sentry.
Thanks for the report. A similar proposal already exists to improve the error log to make it to point to correct file, but I can't seem to find it. Will keep this open for team's tracking.
Use case
Often we encounter in Sentry stacktraces like this one https://github.com/flutter/flutter/issues/151834 In the whole stack trace does not appear one of the source files or our app which is probably due to the fact that the error is happening in the Element tree that is created based on our widget definitions but not in our widgets code.
Proposal
It would be incredibly helpful and time-saving if the flutter framework would offer more information about which widget was the source of a crash. If this information would not need to be included in any exception that the framework throws, It would be enough if we could query some post mortem info before we send the error to sentry.