on beaconManager.startMonitoring(ALL_ESTIMOTE_BEACONS);
java.lang.NullPointerException
at com.estimote.coresdk.scanning.scheduling.KitKatScanScheduler.startOrRestart(KitKatScanScheduler.java:81)
in
com.estimote:sdk:1.0.2
beaconManager.startMonitoring(ALL_ESTIMOTE_BEACONS);
Hi,
are you scanning for Estimote secure beacons? Because you can’t use a SecureBeaconRegion
with an not-defined -it means null
- UUID (see here).
Hi
I am use not secure beacons
this code on Android 6.0 does not cause an exception
Aw, sorry but I can’t solve the problem I’m using Android 5.0.2.
Looks like a possible bug, can you report it on our Android SDK bug tracker? Thanks!
@heypiotr They closed the bug https://github.com/Estimote/Android-SDK/issues/214 but I still saw crash in SDK 1.0.3