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.
I have uploaded one iBeacon(Kontakt) in my Beacon Platform project . I used python sample to upload the same. I used below call for this
pb-cli --service-account-creds creds.json register-beacon --beacon-json '{"advertisedId":{"type":"IBEACON","id":""},"status":"ACTIVE"}' --no-ibeacon-props
Here Encoded Id is generated by encoding iBeacon UDID + Major(Hex) + Minor(Hex)
My iBeacon is uploaded successfully and I can see it in my Beacon Platform dashboard, however I am not able to receive messages in my app which is developed using NearBy samples.
Please note it's working perfectly fine for beacons using eddystone protocol (Kontakt again) which I uploaded using Beacon Tools mobile app. I am using NearBy Message sample for both Foreground and Background mode, and I am getting messages only for eddystone beacon , not for iBeacon.
Are any additional steps needed for iBeacon ?
The text was updated successfully, but these errors were encountered:
to use Nearby Messages you need to add some attachments to your beacon; the Android API fetches these attachments and delivers them as messages (not raw beacon IDs).
Actually I am using attachments. Also everything works for me if I am using Beacon with Eddystone format, I am only seeing issue if I am using iBeacon instead.
Thanks,
Ashutosh
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have uploaded one iBeacon(Kontakt) in my Beacon Platform project . I used python sample to upload the same. I used below call for this
pb-cli --service-account-creds creds.json register-beacon --beacon-json '{"advertisedId":{"type":"IBEACON","id":""},"status":"ACTIVE"}' --no-ibeacon-props
Here Encoded Id is generated by encoding iBeacon UDID + Major(Hex) + Minor(Hex)
My iBeacon is uploaded successfully and I can see it in my Beacon Platform dashboard, however I am not able to receive messages in my app which is developed using NearBy samples.
Please note it's working perfectly fine for beacons using eddystone protocol (Kontakt again) which I uploaded using Beacon Tools mobile app. I am using NearBy Message sample for both Foreground and Background mode, and I am getting messages only for eddystone beacon , not for iBeacon.
Are any additional steps needed for iBeacon ?
The text was updated successfully, but these errors were encountered: