acra/org.acra.config/LimiterConfiguration

LimiterConfiguration

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

LimiterConfiguration

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

deleteReportsOnAppUpdate

val deleteReportsOnAppUpdate: Boolean = true

This property can be used to determine whether old (out of date) reports should be sent or not.

val enabled: Boolean = true

enables this plugin

exceptionClassLimit

val exceptionClassLimit: Int = 10

limit for reports with the same exception class per period

failedReportLimit

val failedReportLimit: Int = 5

limit for unsent reports to keep

ignoredCrashToast

val ignoredCrashToast: String? = null

toast shown when a report was not collected or sent because a limit was exceeded

val overallLimit: Int = 25

general limit of reports per period

val period: Long = 7

number of periodUnits in which to limit reports

val periodUnit: TimeUnit

Unit of period

resetLimitsOnAppUpdate

val resetLimitsOnAppUpdate: Boolean = true

Resetting limits after an app update allows you to see if a bug still exists.

stacktraceLimit

val stacktraceLimit: Int = 3

limit for reports with the same stacktrace per period

Functions

open override fun enabled(): Boolean