You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I am running into some strange behaviour related to scanning for beacons. My use case is to scan for beacons even while a user is not actively using my android app. For this I pass a notification to setForegroundNotification. The issue i run into is that after a while, between 10 - 30 minutes, beacons are no longer be found. From the logs i see multiple messages saying IBeaconUniqueIdCachehas nothing to resolve
I have set the scan period to 2 minutes active and 1 minute passive based on the documentation here but the only thing that seems to resolve this is reinstalling the app. Doing this usually results in beacons being found for an extended period of time (usually a couple of hours) before repeating this behaviour. One additional thing i see in the logs when this happens is:
Context not found for info creator: <my package name>, act: com.kontakt.sdk.android.ble.service.ACTION_FOUND, data: null, type: null, pkg: null, comp: ComponentInfo{<my package name>/com.kontakt.sdk.android.ble.service.BackgroundScanBroadcastReceiver}, categ: null, flag: 0
The device i am using is a Samsung S10+ running Android 12.
The text was updated successfully, but these errors were encountered:
Hello, I am running into some strange behaviour related to scanning for beacons. My use case is to scan for beacons even while a user is not actively using my android app. For this I pass a notification to
setForegroundNotification
. The issue i run into is that after a while, between 10 - 30 minutes, beacons are no longer be found. From the logs i see multiple messages sayingIBeaconUniqueIdCachehas nothing to resolve
I have set the scan period to 2 minutes active and 1 minute passive based on the documentation here but the only thing that seems to resolve this is reinstalling the app. Doing this usually results in beacons being found for an extended period of time (usually a couple of hours) before repeating this behaviour. One additional thing i see in the logs when this happens is:
Context not found for info creator: <my package name>, act: com.kontakt.sdk.android.ble.service.ACTION_FOUND, data: null, type: null, pkg: null, comp: ComponentInfo{<my package name>/com.kontakt.sdk.android.ble.service.BackgroundScanBroadcastReceiver}, categ: null, flag: 0
The device i am using is a Samsung S10+ running Android 12.
The text was updated successfully, but these errors were encountered: