Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

Unable to start bluetooth LE scanner #3

Closed
milesmatthias opened this issue Jun 4, 2018 · 4 comments
Closed

Unable to start bluetooth LE scanner #3

milesmatthias opened this issue Jun 4, 2018 · 4 comments
Labels
native Resolution depends on the native SDK

Comments

@milesmatthias
Copy link

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.

@heypiotr
Copy link
Contributor

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.

@milesmatthias
Copy link
Author

Any update on this and #1 @heypiotr ?

@heypiotr
Copy link
Contributor

I'm still waiting for this to be fixed in the native SDK :(

@heypiotr
Copy link
Contributor

heypiotr commented Aug 3, 2018

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.

@heypiotr heypiotr closed this as completed Aug 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
native Resolution depends on the native SDK
Projects
None yet
Development

No branches or pull requests

2 participants