CODEWITHSUNDEEP
androidgoogle-nearby
RobM
RobM

Reputation: 111

Nearby notification debugging

I have bought a beacon (#1) and registered it via the google beacon dashboard and added a nearby notification with a https web url. Using my android device running marshmallow I was regularly getting nearby notifications a week ago.

Since then the notifications during testing have reduced. And for the past two days I have had no notifications at all from the beacon. The beacon is 50cm from my android device and is discoverable from all 3rd part beacon scanners that I have installed. I have two other android devices which I use for test. They do not get nearby notifications recently either.

I've set up a fresh beacon (#2) and registered it via the google beacon dashboard and added another nearby notification but using a different https address ( https address #2 ). This gets notifications ok on all devices.

And so I take https address #2 and use it for the weburl on beacon #1 and now I get notifications from beacon #1 using https address #2

This leads me to believe that https address #1 is being filtered for some reason. But I need https address #1 to work to demonstrate to my potential customer.

My question is how can I debug why https address #1 does not work after a while. Or infact will all addresses stop working after a week or so. Is there any way to debug the black box between the beacon dashboard and my android device?

my follicle crop has been reduced significantly this week. Its a resource I am light on.

Upvotes: 0

Views: 252

Answers (1)

Tony Tran
Tony Tran

Reputation: 234

I work on Nearby and there are two possibilities on why the notification for address #1 no longer shows up

  1. There's notification back off policy in place where if the notification is shown multiple times and user did not interact with it, we'll back it off and eventually not show the notification. This policy will reset if you go to the list view via (Settings -> Google -> Nearby)

    • Check list view ie. Nearby via (Settings -> Google -> Nearby) to see if you can still see the item there.
    • Note: we will make sure to update our documentation about this back off policy.

  2. The url or its content may have triggered some filtering on our side. If you let me know what the url is then I can check to confirm.

Upvotes: 0

Related Questions