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

No way of CLBeacon and KTKNearbyDevice matching #89

Open
devberkay opened this issue Jun 30, 2023 · 0 comments
Open

No way of CLBeacon and KTKNearbyDevice matching #89

devberkay opened this issue Jun 30, 2023 · 0 comments

Comments

@devberkay
Copy link

devberkay commented Jun 30, 2023

I don't understand how to match CLBeacon object with related KTKNearbyDevice object. Let's say i have a beacon and its CoreLocation infos(proxUUID, major and minor) are provided through didRange listener. This listener only provides detected CLBeacon objects which only provides proxUUID, major and minor. But to match my users with specific beacons, i need some kind of a uid related with that beacon. It seems that is being provided via Secure profile packages, but those packages are provided through KTKNearbyDevice object and has no indicator to match related CLBeacon object. So , how do we create a compound object having proxUUID,major,minor,rssi (CoreLocation related infos) with Device name, device uid, macAdress etc (CoreBluetooth infos). I initially thought secureprofile packages are provided for this but it only provides CoreBluetooth related infos. Then what's the point of having those secure profile packages other than making write operations on the beacon?

@devberkay devberkay changed the title CLBeacon and KTKNearbyDevice matching and having no convenient way to identify beacons No way of CLBeacon and KTKNearbyDevice matching Jun 30, 2023
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

No branches or pull requests

1 participant