Closed anthonytw closed 1 year ago
Thanks for working on this. At the time I wrote this, 32-bit UUID's were not in common use, and were unsupported by many implementations. Could you describe the use case you encountered in which 32-bit UUID's are used?
I don't know that anyone uses them officially, as far as I can tell you can't even register a 32-bit UUID right now. But, I guess since people can use them, it seems at least some people are. This became an issue running scanning code on my university campus where, any time it encountered a 32-bit UUID (albeit this is rare), it would raise an exception and I'd have to restart the scan. I have no idea what devices are using that feature, but might as well add support for it to avoid weird errors.
The BLE spec sets aside standard 16- and 32-bit UUIDs, but the library currently only supports 16-bit UUIDs. If a 32-bit UUID is encountered in the wild the package raises an exception. Support for 32-bit UUIDs should be added.