You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should be a way to disable the forceful nature of some sentry defaults being inserted for transactions
Motivation
#570 is an issue with concurrent writes caused by sentry's transaction submission code. SDK tries to be useful and inserts data which isn't accurate to the context of the user. In our case we have access to device model but not CPU, arch etc, (which we don't have access to) so sentry will insert that automatically, but it ends up crashing the application instead. Crash rate is low, but still non-zero and that shouldn't be acceptable from a library of error reporting tools.
The text was updated successfully, but these errors were encountered:
Summary
There should be a way to disable the forceful nature of some sentry defaults being inserted for transactions
Motivation
#570 is an issue with concurrent writes caused by sentry's transaction submission code. SDK tries to be useful and inserts data which isn't accurate to the context of the user. In our case we have access to device model but not CPU, arch etc, (which we don't have access to) so sentry will insert that automatically, but it ends up crashing the application instead. Crash rate is low, but still non-zero and that shouldn't be acceptable from a library of error reporting tools.
The text was updated successfully, but these errors were encountered: