Keeping scan even if I stopped service

Expected behavior

Stopping scan and not detection

Actual behavior

After I call that lines

beaconManager.removeAllRangeNotifiers()
beaconManager.disableForegroundServiceScanning()

I still see that logs

D/BeaconParser: Processing pdu type FF: 0201***** with startIndex: 5, endIndex: 29
D/BeaconParser: This is a recognized beacon advertisement -- 02 15 seen
D/ScanHelper: Beacon packet detected for: id1: 7427**** id2: 10 id3: 7 with rssi -82
D/BeaconParser: Bytes are: 0201*****
D/ScanHelper: beacon detected : id1: 7427**** id2: 10 id3: 7
D/ScanHelper: looking for ranging region matches for this beacon
D/ScanHelper: matches ranging region: id1: null id2: null id3: null
D/RangeState: adding id1: 7427**** id2: 10 id3: 7 to existing range for: org.altbeacon.beacon.service.RangedBeacon@1fd3a03
D/ScanHelper: Beacon packet detected for: id1: 7427**** id2: 10 id3: 7 with rssi -82
D/ScanHelper: beacon detected : id1: 7427****: 10 id3: 7

Steps to reproduce this behavior

I’m definitely sure that services is not running after I stopped. I checked my working services under Developer options and I saw my services is not running. So, where does this logs come from? Additionally, I start stop service in twice, also logs goes twice.

I think when I stop the service, it’s keeping queue the scans and when I start again, I takes also stopped service events and fires multiple at 1100 seconds

Mobile device model and OS version

Samsung Galaxy J5 Prime- OS 8.0.0

Android Beacon Library version

2.15.4

[TayfunCesur]

Waow. Didn’t think that. Thank you so much @paulpv

[paulpv]

@TayfunCesur FYI, I have noticed that if you decorate your dependencies implementation lines with closures then gradle will not warn you that there is a new version available. If you comment out any decorating closure then gradle should warn you that there is a new version available. Seems like a weak sauce bug in Gradle. 😕