search

google / eddystone

Specification for Eddystone, an open beacon format from Google
Apache License 2.0
3.07k stars 761 forks source link

Nearby notifications not working? #226

Open justinbelobaba opened 6 years ago

justinbelobaba commented 6 years ago

Hi - I have deployed several thousand beacons using Google Nearby. We can see that the beacons are working, and they are showing up in the Nearby app. However, as of 2pm yesterday, none of them are generating Nearby notifications (on the Android notification pull-down screen). Is there something going on? Thanks!

itsmeritesh commented 6 years ago

Are you seeing notifications in debug mode? Can you share a beacon id ?

justinbelobaba commented 6 years ago

Hi there - yes, we get nearby notifications properly in debug mode (on notification screen & in nearby app). But not in production (nearby app works, but notification screen does not show notification).

Example: 3!f7826da6bc5b71e0893e7149516b6449

This beacon worked properly in debug but not production.

laccf commented 6 years ago

Hello, @justinbelobaba . Are you using UID or EID frame?

justinbelobaba commented 6 years ago

Hi @laccf - we are using UID.

laccf commented 6 years ago

I get this issue when a beacon gets low and I have to change the battery, the Google Api can't resolve anymore the EID.

Does your app recognize this beacon? Did you try oauthplayground to see if your beacon is still registered? One of the problems that I had using nearby notification was about the compatibility of the language of the cellphone that receive the notification and the language that you set on the google console. It has to be the same.

justinbelobaba commented 6 years ago

Thanks very much - will try!

parab-aditya commented 6 years ago

Hi @justinbelobaba , If you have deployed several thousand beacons and it works in debug, then probably you are getting limited by the API quota. You will need to contact Google to increase the API calls limit. Also like @laccf said, try making a call in oauthplayground and see if that works.

laccf commented 6 years ago

If your quota has ended, you will get error 429.

parab-aditya commented 6 years ago

Yes thats correct. Also, for some reason, it doesn't let me apply for higher quote. When I click the link, it opens a Google form link and says this "You need permission This form can only be viewed by users in the owner's organization. Try contacting the owner of the form if you think this is a mistake."

Have any of you been able to apply for higher quote? I am using my personal gmail account. (not under an organization)

justinbelobaba commented 6 years ago

@parab-aditya @laccf thank you both!

laccf commented 6 years ago

@parab-aditya I updated my quota, but nothing relevant. Here there is a link that you can read a little about quotas.

parab-aditya commented 6 years ago

@laccf I tried updating, can't seem to get past that Google form "No permission" message. Tried asking Google Cloud about it, and they said to post on SO :/ (https://stackoverflow.com/questions/46082745/cannot-increase-google-proximity-api-quota)

oirishred commented 6 years ago

Justin I have some of your beacons and landed here looking to solve the same issue. What solution did you find?

justinbelobaba commented 6 years ago

We were able to resolve the issue.

Justin

On Oct 14, 2017, at 1:34 AM, oirishred notifications@github.com wrote:

Justin I have some of your beacons and landed here looking to solve the same issue. What solution did you find?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

oirishred commented 6 years ago

Then please tell me why I'm still having the issue or send someone my way who can help. Thanks

On Oct 14, 2017 10:15 AM, "jus23tin" notifications@github.com wrote:

We were able to resolve the issue.

Justin

On Oct 14, 2017, at 1:34 AM, oirishred notifications@github.com wrote:

Justin I have some of your beacons and landed here looking to solve the same issue. What solution did you find?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/google/eddystone/issues/226#issuecomment-336637557, or mute the thread https://github.com/notifications/unsubscribe-auth/AfRN25IS2NSIVnH6K3VrMcWR8vApOsUJks5ssMIFgaJpZM4O40NH .

justinbelobaba commented 6 years ago

Email support@royaltie.com

Sent from my iPhone

On Oct 15, 2017, at 6:25 AM, oirishred notifications@github.com wrote:

Then please tell me why I'm still having the issue or send someone my way who can help. Thanks

On Oct 14, 2017 10:15 AM, "jus23tin" notifications@github.com wrote:

We were able to resolve the issue.

Justin

On Oct 14, 2017, at 1:34 AM, oirishred notifications@github.com wrote:

Justin I have some of your beacons and landed here looking to solve the same issue. What solution did you find?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/google/eddystone/issues/226#issuecomment-336637557, or mute the thread https://github.com/notifications/unsubscribe-auth/AfRN25IS2NSIVnH6K3VrMcWR8vApOsUJks5ssMIFgaJpZM4O40NH . — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

parab-aditya commented 6 years ago

Can you please kindly post your solution and how you resolved this issue?

On Oct 14, 2017 7:45 PM, "jus23tin" notifications@github.com wrote:

We were able to resolve the issue.

Justin

On Oct 14, 2017, at 1:34 AM, oirishred notifications@github.com wrote:

Justin I have some of your beacons and landed here looking to solve the same issue. What solution did you find?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/eddystone/issues/226#issuecomment-336637557, or mute the thread https://github.com/notifications/unsubscribe-auth/ANBzM_RZNsZFKVZZuZhcIMgtvyOILPMKks5ssMIFgaJpZM4O40NH .

justinbelobaba commented 6 years ago

Pretty simple actually: avoid personally identifiable information in the messages.

On Sun, Oct 15, 2017 at 8:55 AM, Aditya Parab notifications@github.com wrote:

Can you please kindly post your solution and how you resolved this issue?

On Oct 14, 2017 7:45 PM, "jus23tin" notifications@github.com wrote:

We were able to resolve the issue.

Justin

On Oct 14, 2017, at 1:34 AM, oirishred notifications@github.com wrote:

Justin I have some of your beacons and landed here looking to solve the same issue. What solution did you find?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/eddystone/issues/226#issuecomment-336637557, or mute the thread https://github.com/notifications/unsubscribe-auth/ANBzM_ RZNsZFKVZZuZhcIMgtvyOILPMKks5ssMIFgaJpZM4O40NH

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/eddystone/issues/226#issuecomment-336709751, or mute the thread https://github.com/notifications/unsubscribe-auth/AdoPPTPz-2tPvNvOKpBPVKwMI5_t8yltks5ssgC-gaJpZM4O40NH .

--

Justin Belobaba ,

CEO, Royaltie mobile: address:

royaltie.com

This e-mail may be privileged and/or confidential and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise the sender (by return e-mail or otherwise) immediately.

parab-aditya commented 6 years ago

That is really vague on Google's side. There should be some criterias to judge that, and if you have a couple of clients for your project, how do you control what messages they broadcast? But the weird part this doesn't just happen to one beacon, rather the entire project. And in case you have a couple thousand deployed, you are pretty much done there