Closed justinelsberry closed 10 years ago
No, this is nothing to be concerned about. Next version will have less noise in the logs.
The reason you are seeing that is library scans for all Bluetooth Low Energy beacons and finds Estimote ones. If you have device like Pebble watch, you can see this log as not Estimote one. That's that all.
Everything appears to be working correctly - I get both monitoring and ranging callbacks but I see this error in logcat every second. This is on a S4 with Android 4.4.2. Is this something to be concerned with?
com.estimote.sdk.service.BeaconService$InternalLeScanCallback.onLeScan:416 Parse error: 0201061106ba5689a6fabfa2bd01467d6e00fbabad05160a1808060609466f726365020afa00000000000000000000000000000000000000000000000000