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 Dec 29, 2022. It is now read-only.
I have been trying to use Google Beacon Platform's Nearby Notification using multiple web url's and multiple app intents. At first I used to receive the last modified or added notification but after few tries I am getting randomized notifications i.e. either web url's notification or app intent notification whenever I turn on the Bluetooth in my device. Is there a valid reason like, if is there fixed duration for a particular notification for this or is it the beacon's fault ?
Targeting rule is set to default for all entries.
Could anyone help me with this?
Thank You in advance :)
The text was updated successfully, but these errors were encountered:
It is my understanding that the beacons only broadcast one attached message at a time, unless it is set up to broadcast multiple protocols (e.g. eddystone-URL and Eddystone-UID) in which case it is possible to have two things broadcast at once.
Some devices allow for multiple broadcast slots and can have eddystone-UID set up in multiple slots. You then register each slot to Google beacon platform as a separate device.
It sounds like you have eddystone-UID set up with multiple attachments (URL and intent), but because only one can be broadcast at a time it is randomly pulling an attachment each time.
Setting a target will allow you to set a time and date for broadcast, it may help.
I have been trying to use Google Beacon Platform's Nearby Notification using multiple web url's and multiple app intents. At first I used to receive the last modified or added notification but after few tries I am getting randomized notifications i.e. either web url's notification or app intent notification whenever I turn on the Bluetooth in my device. Is there a valid reason like, if is there fixed duration for a particular notification for this or is it the beacon's fault ?
Targeting rule is set to default for all entries.
Could anyone help me with this?
Thank You in advance :)
The text was updated successfully, but these errors were encountered: