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
We are using Sentry in our Android app. The app is written in Kotlin and makes use of the arrow.kt library to handle errors (among other things). However, those errors are spamming the issues list for the app on Sentry. My understanding is that handled errors should not be reported as issues automatically. Because they are, I seem to be exceeding the quotas for my project too soon. Does anyone know where the issue could be coming from?
Here is an example of how errors are handled in our app:
val foo = ...
either {
ensureNotNull(foo) {
NullPointerException("Foo not set.")
}
}.fold({ ... }) { ... }
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are using Sentry in our Android app. The app is written in Kotlin and makes use of the arrow.kt library to handle errors (among other things). However, those errors are spamming the issues list for the app on Sentry. My understanding is that handled errors should not be reported as issues automatically. Because they are, I seem to be exceeding the quotas for my project too soon. Does anyone know where the issue could be coming from?
Here is an example of how errors are handled in our app:
Beta Was this translation helpful? Give feedback.
All reactions