App stops scanning right after screen is locked and starts giving the results right after unlocked

[Suraj-Japptech]

Expected behavior

Whenever I lock the mobile while the app is in foreground the app should scan custom beacons as it was doing when it is in the foreground.

Actual behavior

The app is in foreground and i can see the beacons listing then i have pressed the power button to lock the device , right after I locked the device the library stops scanning custom beacons. But from the logs I can see that it is scanning and it returns some device's has value which is not one of our beacons so that the parser cannot decode the hash value .

And I notice that right after I lock the mobile the library is showing outside of beacon region in the monitoring observer.

Steps to reproduce this behavior

Run the app and keep the app in foreground and press the power button to lock to mobile and observe the logs.

Mobile device model and OS version

Samsung galaxy tab A7
model : SM-T505
Android OS version : 12

Android Beacon Library version

org.altbeacon:android-beacon-library:2.19.5

[davidgyoung]

Please attach logs that show this: "But from the logs I can see that it is scanning and it returns some device's has value which is not one of our beacons so that the parser cannot decode the hash value ." I would like to see logs when your custom beacon is detected, and logs for when it is not detected, but other bluetooth devices are.