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.

Sign up for GitHub

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

Jump to bottom

Investigate 16-bit UUID shenanigans with SwiftyTooth #63

Open

sureshjoshi opened this issue Oct 30, 2023 · 1 comment

Labels

bug

Member

sureshjoshi commented Oct 30, 2023 •

edited

Loading

In a project with a sample peripheral, when I expose the a 16-bit service and 16-bit UUID, my Nordic NRF52 isn't picking it up in directed discovery.

When I expand it to 128-bits, it's still not being picked up.

If I change any random char, it's picked up perfectly.

Seems to be some weirdness with the well-known UUIDs, probably coming from CoreBluetooth, or SwiftyTooth.

Also, the UUID is picked up if I do an unconstrained search on all UUIDs, so it's something specifically about filtering by 16-bit UUID.

sureshjoshi added the bug label

Member Author

sureshjoshi commented Oct 30, 2023

This is another +1 for #62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment