Background service notification doesn't go away on proximityHandler.stop()

rjain90 commented 5 years ago

Prerequisites

[X ] 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)
- My Android device/devices supports BLE and has Android OS version >= 5.0.0
- My Android device/devices have bluetooth enabled
- My app has Location Permissions granted

Basic information

Estimote SDK version: proximity-sdk:1.0.3

Android devices affected: OnePlus 3T

Android OS version affected: Android Oreo 8.0.0

Beacon hardware version: mint

Description

I have enabled Background scanning using foreground service in my app and the SDK shows the notification when the app start observing for the beacons. But when the app calls proximityHandler.stop(), the notification doesn't go away. Can someone guide me as to how I can get rid of this notification once I stop looking for beacons.

Expected behavior: The notification should go away as soon as proximityHandler.stop() is called

Actual behavior: The notification stays there

rjain90 commented 5 years ago

Can anyone help?

abiela commented 5 years ago

Hey @rjain90,

We investigated the test scenario you described on Android 8.0.0 with foreground service usage. We didn't observe any troubles with proper notification handling when performing start/stop zone observing.

Please double check if you hold the ProximityObserver.Handler object correctly. You shouldn't lose any handler reference without proper stop() method invocation.

Sharing a code snippet with ProximityObserver.Handler handling can be helpful to understand better the reason for unexpected behavior.

Estimote / Android-Proximity-SDK