Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

readCharacteristic() doesn't return fail callback #51

Closed
alexisduque opened this issue Jan 21, 2015 · 3 comments
Closed

readCharacteristic() doesn't return fail callback #51

alexisduque opened this issue Jan 21, 2015 · 3 comments
Labels

Comments

@alexisduque
Copy link

When I call readCharacteristic() on a peripheral implementing PASSKEY security, Android often doesn't ask for passkey.

So readCharacterstic failed but neither success nor error callback are called.
However, using logcat, I can see that the API returns GATT_INSUFFICIENT_AUTHENTICATION (status = 5)
D/BluetoothGatt(23821): onCharacteristicRead() - Device=FD:8B:BA:4B:1D:27 UUID=f3851521-5942-b2cb-ae40-271cd0dd17e5 Status=0

@fredrikeldh
Copy link
Contributor

I think this a bug in Android; my handler calls the error callback when it gets any status except SUCCESS.

@fredrikeldh
Copy link
Contributor

On second thought, we might add a timeout of our own. Wouldn't report the proper error code, but at least it would report some error.

@ghost
Copy link

ghost commented Nov 24, 2016

There is now support for explicit paring/bonding in the BLE plugin, that should help with this issue.

There are however reports of that this works a bit unstable, not sure if this is the plugin or the Android implementation. See this issue: #129

Closing this issue, let me know if to reopen.

@ghost ghost closed this as completed Nov 24, 2016
@ghost ghost removed the unfixable label Nov 24, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants