Skip to content
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.

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

Running blesh scan panics on MacOS when a nearby device has a 32bit UUID #97

Open
linden opened this issue May 17, 2022 · 0 comments · May be fixed by #98
Open

Running blesh scan panics on MacOS when a nearby device has a 32bit UUID #97

linden opened this issue May 17, 2022 · 0 comments · May be fixed by #98

Comments

@linden
Copy link

linden commented May 17, 2022

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/[email protected]/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/[email protected]/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).

@linden linden linked a pull request May 17, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant