These values have dependencies within and between each other which hence demand more effort right now to test thoroughly
For example the error of number 3 of the list below 1) does not occur while setting the configuration, but when starting to scan and 2) is somehow not catched by the try-catch-loop inside the startScanning method of the ScanManager class and causes the app to crash (Perhaps have to try to include a nested try-catch inside onServiceReady here..)
Some of the value dependencies:
The active scan period must be a positive value equal or longer than 3000 ms
The passive scan period must be a positive value equal or higher than 2000ms or equal to 0.
Activity check period must be shorter than active scan period #(https://github.com/kontaktio/kontakt-android-sdk/issues/145) , i.e. the first argument activePeriod of scanPeriod has to be greater than the second argument checkPeriod of activityCheckConfiguration.
Not added for now because it's not stable yet.
Some details:
startScanning
method of theScanManager
class and causes the app to crash (Perhaps have to try to include a nested try-catch insideonServiceReady
here..)Some of the value dependencies:
activePeriod
ofscanPeriod
has to be greater than the second argumentcheckPeriod
ofactivityCheckConfiguration
.