Scanner stops working after a while

[JDW-Syscom]

Prerequisites

• [ ] Put an X between the brackets on this line if you have done all of the following:
  • My beacons have Estimote Monitoring enabled (Check it in the Estimote Cloud, or via app)
  • [x] My Android device/devices supports BLE and has Android OS version >= 5.0.0
  • [x] My Android device/devices have bluetooth enabled
  • [x] My app has Location Permissions granted

Basic information

Estimote SDK version: 1.0.5

Android devices affected: Samsung Galaxy S10

Android OS version affected: 10

Beacon hardware version: J1.9_B1.1

Description

When using a foreground Service the scanner can stop working. It will trigger an on exit and then after that nothing will happen anymore. The notification is still there saying it's scanning. This happens when you press the home button and leave it for a while, I managed to trigger this more quickly just after rebooting my phone then starting the app & scan.

I'm using the template for Proximity for Multiple Beacons & added a notification for the foreground service.

(Optional) Steps to reproduce:

1. (Optional, might be quicker) Reboot phone
2. Start Scanner with a foreground service
3. Press home button (maybe lock phone even)
4. An on enter should trigger
5. After a while, without moving anything an exit should trigger
6. Can not enter or leave other zones

Expected behavior: Scanning should continue without being interrupted

Actual behavior: Scanner triggers an exit zone and may never be able to enter it again.

Additional information

I noticed that when you have a second app with the same credentials, you start the scanner on that second app then the first might work again (for a while)

Might be related to https://github.com/Estimote/Android-Proximity-SDK/issues/89

[Shailevy]

+1 Same here, reproduced on many devices. any updates on this ?