Piotr Krawiec

There's really two problems here: 1. The SDK crashing when an error happens, instead of propagating the error to the `onError` handler like expected. @IreneTrullen shared a work-around for that...

Hey @vardaan, please see my explanation of the root cause of the "error code 2". https://forums.estimote.com/t/postlollipopestimotescanner-kt-line-29/9745/2?u=heypiotr If you're getting this error in your production app, it's very likely that you're...

This is actually a bigger on-going debate we're having within the Proximity SDK team. Our problem with an API for distance is, the distance estimations based on BLE signal strength...

Not including it was a design decision on our side. Based on our experience, we consider building interactions based on the distance (which is very finicky for Bluetooth-signal-based estimations) to...

Gotcha, I think I understand your case, and I can see how passing the zone's metadata (incl. the trigger range) to the enter/exit/change listeners could be useful if you want...

Probably best discussed on the native SDKs' bug trackers and/or Estimote Forums, since these are changes that would need to be implemented on the native side. A "knob" for the...

It's really tough to say, I'd actually expect that for the best results, the numbers would need to be tuned almost per device. There's been ideas/efforts to crowd-source this knowledge,...

Does this only happen on some specific smartphone + Android version combo? Or are you able to reproduce it with different devices?

Mhmm, I can't reproduce this on my Androids, so this could be something specific to your app. Mind sharing the bits of the code where you setup and start the...

And what Android device and version is that? Can you try some other app that uses Bluetooth Low Energy scanning? For example, [nRF Connect](https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp&hl=en). Just trying to rule out some...