You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2022. It is now read-only.
The sample works only for Eddystone beacons, but I want to use some iBeacons that can't support Eddystone. Could this sample include support for them please?
Also, I must say what to put in "id" here for an iBeacon is not clear as iBeacons have 3 values, not one (an UUID, a major and a minor values).
The text was updated successfully, but these errors were encountered:
The AdvertisedId field for the Proximity Beacon API just uses the concatenated UUID + major + minor of the iBeacon format. Take those 16 + 2 + 2 bytes as a byte array of length 20, then Base64 the it to get the string you send.
Unfortunately, It's not enough to add a scan filter as the app must be able to recognize eddystone.
i'm currently using the code I found here, but I have yet to finish adding it to the sample successfully.
Why isn't this already included in the sample OOB?
Why require all developers to waste their time against this while it could just be a merged pull request?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
The sample works only for Eddystone beacons, but I want to use some iBeacons that can't support Eddystone. Could this sample include support for them please?
Also, I must say what to put in "id" here for an iBeacon is not clear as iBeacons have 3 values, not one (an UUID, a major and a minor values).
The text was updated successfully, but these errors were encountered: