Limiter Configuration
class LimiterConfiguration(val enabled: Boolean = true, val periodUnit: TimeUnit = TimeUnit.DAYS, val period: Long = 7, val overallLimit: Int = 25, val stacktraceLimit: Int = 3, val exceptionClassLimit: Int = 10, val failedReportLimit: Int = 5, val ignoredCrashToast: String? = null, val deleteReportsOnAppUpdate: Boolean = true, val resetLimitsOnAppUpdate: Boolean = true) : Configuration
Limiter configuration
Author
F43nd1r
Since
26.10.2017
Constructors
Link copied to clipboard
constructor(enabled: Boolean = true, periodUnit: TimeUnit = TimeUnit.DAYS, period: Long = 7, overallLimit: Int = 25, stacktraceLimit: Int = 3, exceptionClassLimit: Int = 10, failedReportLimit: Int = 5, ignoredCrashToast: String? = null, deleteReportsOnAppUpdate: Boolean = true, resetLimitsOnAppUpdate: Boolean = true)
Properties
Link copied to clipboard
This property can be used to determine whether old (out of date) reports should be sent or not.
Link copied to clipboard
limit for reports with the same exception class per period
Link copied to clipboard
limit for unsent reports to keep
Link copied to clipboard
toast shown when a report was not collected or sent because a limit was exceeded
Link copied to clipboard
general limit of reports per period
Link copied to clipboard
number of periodUnits in which to limit reports
Link copied to clipboard
Unit of period
Link copied to clipboard
Resetting limits after an app update allows you to see if a bug still exists.
Link copied to clipboard
limit for reports with the same stacktrace per period