Skip to content
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.

Android O: requestUuid is always null #112

Open
lesn1kk opened this issue Aug 18, 2017 · 0 comments
Open

Android O: requestUuid is always null #112

lesn1kk opened this issue Aug 18, 2017 · 0 comments

Comments

@lesn1kk
Copy link
Member

lesn1kk commented Aug 18, 2017

On Android O we are unable to resolve our own mac address using BRO mode because the Gatt client requestUuid is always null and since we use it to compare with expected uuid, the condition will never be fulfilled (see here).
I noticed however, that the mServiceUuid first 24 characters (as string) are the same as bluetoothGattCharacteristic.getUuid()'s. But I don't know if it has something to do with BRO mode specific UUID or anything else.
Anyway, when I compared bluetoothGattCharacteristic.getUuid() and mServiceUuid first 24 chars instead of bluetoothGattCharacteristic.getUuid() and requestUuid, I was able to resolve device's own BT mac address.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant