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
{{ message }}
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.
Some devices don't support bluetooth LE scanning, but the Estimote SDK doesn't provide a way to catch that error and do something. Instead, I'm just seeing a Java error:
java.lang.IllegalStateException
Unable to create bluetooth LE scanner instance
An onError callback with a message of "device unsupported" or something like that is what we need, instead of a Java exception being raised.
The text was updated successfully, but these errors were encountered:
Just realized I've never replied to this one, so I just want to assure you we've seen it the day you posted it, and it's something to be addressed in the native Android Proximity SDK.
In fact, now that I think about it, it's somewhat related to #1: currently there's a bug where the exceptions to be reported to the onError handler get thrown instead.
I'll leave both open for the time being though, since they're two different use cases.
In 0.4.0, the app will no longer crash on onError. This doesn't entirely solve the problem of "how do I know/handle BLE unsupported or Bluetooth off/state changes", but let's track that in #9.
Some devices don't support bluetooth LE scanning, but the Estimote SDK doesn't provide a way to catch that error and do something. Instead, I'm just seeing a Java error:
An onError callback with a message of "device unsupported" or something like that is what we need, instead of a Java exception being raised.
The text was updated successfully, but these errors were encountered: