[TIMOB-23267] Hyperloop: Android - Unable to call method accepting byte[] argument
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2016-04-27T16:06:40.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 5.4.0 |
Components | Android, Hyperloop |
Labels | android, hyperloop, needTestCase |
Reporter | Brian García |
Assignee | Christopher Williams |
Created | 2016-04-22T14:32:33.000+0000 |
Updated | 2018-08-06T17:49:30.000+0000 |
Description
descriptor.setValue(BluetoothGattDescriptor.ENABLE_NOTIFICATION_VALUE);
results in:
HyperloopProxy: (main) [3454,3454] Unable to resolve method call. Class: android.bluetooth.BluetoothGattDescriptor, method name: setValue, args: [[Ljava.lang.Object;@3f4
See http://developer.android.com/reference/android/bluetooth/BluetoothGattDescriptor.html#setValue(byte[])
[~bgarcia] Can you please add a simplified test-case with the expected behavior here so QE can verify the fix as well?
this is a difficult one... theoretically if you can get a descriptor from a BLE device (after a ble scan, retrieving device characteristics) just :
Mhh, ok.
descriptors
would be undefined in the above example. Another method that would accept abyte[]
argument which our QE could test? I'm not too familiar with Android.mmm neither do I... may be cwilliams could help
Cleaning up older fixed issues. If this issue should not have been closed as fixed, please reopen.