-
Notifications
You must be signed in to change notification settings - Fork 582
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
Introduce operation viability checks prior to execution #224
Comments
dariuszseweryn
pushed a commit
that referenced
this issue
Aug 3, 2017
Implemented a mechanism for checking whether the requested characteristic operation can succeed. The check is based upon the properties of the chosen characteristic. End user can opt-out of the 'hard' way of checking (ie. throwing an exception) using new connection setup API.
dariuszseweryn
added a commit
that referenced
this issue
Aug 3, 2017
…lishConnection(SetupOptions)` (#240 #224) This new function is a perfect extension point to introduce a new public API #239 which will return the new API without changing the Major version number. Till then all new public classes were moved to the `internal` package and should not be publicly available.
The viability check will result in a log warning in |
dariuszseweryn
added a commit
that referenced
this issue
Aug 3, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Sometimes user tries to execute an operation of type that is not supported by a characteristic which ends with not easily understandable error like
BluetoothGattException
with some status code.Preconditions
A characteristic that only supports indications.
Steps to reproduce actual result
1. Connect to a device
2. Discover services
3. Setup notifications on the characteristic
4. Observe error with
status=128
Logs from the application running with setting
RxBleLog.setLogLevel(RxBleLog.VERBOSE)
Actual result
06-18 17:44:56.731 19237-19249/com.mypackage D/RxBle#BluetoothGatt: onDescriptorWrite descriptor=00002902-0000-1000-8000-00805f9b34fb status=128
Expected result
Easily understandable error
The text was updated successfully, but these errors were encountered: