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
Currently, when the library user configures scan periods for background scanning, the library discards the backgroundBetweenScanPeriod, and uses the backgroundScanPeriod for that instead. This is present in 2 places in BeaconManager class, both in the applySettingsChange method.
Line 258
Line 275
Also, while I am not sure of this, the default value for backgroundBetweenScanPeriod in Settings.kt file, ScanPeriods data class should not be 0.
Thanks for this report, @elican-doenyas. This is a bug and needs to be fixed. Would you like to submit a Pull Request with this change? I will gladly merge.
We can also change the default value for the backgroundBetweenScanPeriod in Settings.kt to be 300000 ms (5 minutes) which matches the default elsewhere in the library.
Currently, when the library user configures scan periods for background scanning, the library discards the backgroundBetweenScanPeriod, and uses the backgroundScanPeriod for that instead. This is present in 2 places in BeaconManager class, both in the applySettingsChange method.
Also, while I am not sure of this, the default value for backgroundBetweenScanPeriod in Settings.kt file, ScanPeriods data class should not be 0.
@davidgyoung thanks in advance.
The text was updated successfully, but these errors were encountered: