Currently when you run blesh scan on MacOS it'll panics when it sees a 32bit UUID, this is due to the lack of 32bit UUID support in cbgo.
There is a pull request fixing this (JuulLabs-OSS/cbgo#3) but it has not yet been merged.
Here's what the logs look like when it finds a 32bit UUID.
Initializing device ...
Scanning for 5s...
[... scan omitted ...]
panic: invalid UUID string: DAF51C01
goroutine 17 [running, locked to thread]:
github.com/JuulLabs-OSS/cbgo.mustStrArrToUUIDs(...)
/Users/linden/go/pkg/mod/github.com/!juul!labs-!o!s!s/cbgo@v0.0.1/cutil.go:124
github.com/JuulLabs-OSS/cbgo.BTCentralManagerDidDiscoverPeripheral(0x600000534080, 0x600001a2c000, 0x16bdfa4b8, 0xffffffb6)
/Users/linden/go/pkg/mod/github.com/!juul!labs-!o!s!s/cbgo@v0.0.1/cbhandlers.go:77 +0x3a4
exit status 2
I'd recommend just directly using the patch provided in the pull request until it's merged (or creating a fork as cbgo seems to be abandoned).
Currently when you run
blesh scanon MacOS it'll panics when it sees a 32bit UUID, this is due to the lack of 32bit UUID support in cbgo.There is a pull request fixing this (JuulLabs-OSS/cbgo#3) but it has not yet been merged.
Here's what the logs look like when it finds a 32bit UUID.
I'd recommend just directly using the patch provided in the pull request until it's merged (or creating a fork as cbgo seems to be abandoned).