Unexpected new behavior: startRangingBeacons in BeaconManager must be called on the main thread

[gerardmundo-birket]

This change probably comes from commit 6c0aa93 "Merge branch 'bugfix/repeadly-scan-job-restart-on-navigation'"

Expected behavior

No crash when calling startRangingBeacons from a non-UI thread. This was the case until pulling "recent" code changes.

Actual behavior

Crash
java.lang.IllegalStateException: Method addObserver must be called on the main thread
at androidx.lifecycle.LifecycleRegistry.enforceMainThreadIfNeeded(LifecycleRegistry.kt:296)
at androidx.lifecycle.LifecycleRegistry.addObserver(LifecycleRegistry.kt:174)
at org.altbeacon.beacon.powersave.BackgroundPowerSaverInternal.(BackgroundPowerSaverInternal.java:44)
at org.altbeacon.beacon.BeaconManager.ensureBackgroundPowerSaver(BeaconManager.java:2088)
at org.altbeacon.beacon.BeaconManager.startRangingBeacons(BeaconManager.java:1186)

Steps to reproduce this behavior

Call startRangingBeacons from a non-UI thread

Mobile device model and OS version

Samsung Galaxy Tab Active2 on Android 8.1.0

Android Beacon Library version

Latest code in repo

IMPORTANT: This forum is reserved for feature requests or reproducible bugs with the library itself. If you need help with using the library with your project, please open a new question on StackOverflow.com.

[VolodaUa]

Hi @gerardmundo-birket

Thanks for noticing it. I've created the pull request.