register beacon return 403, permission_denied error

[naren]

I taken the Android-nRF-Beacon-for-Eddystone app code from github.

From my account I configured my Google Dev console:

1. enabled proximity API

2. added credentials for OAuth2.0 and Client ID. Based on the SHA1 code of my machine.

[naren]

I am using Nexus 4 and Nexus 7, with Android L and Android M respectively, for me also Google Play services are crashing every time, and every time I am getting 403 error while registering and some time It's even fail to connect to Beacon.

[Aleksander Nowakowski]

That's good... looks like GPS have a bug, or hey changed some API and asking for permission needs to be done differently now. When we were developing the app GPS were asking for permission to use Proximity API just like they do for the shortener. I will write a message about it to Google Eddystone team and wait for their reply. Sorry for inconvenience.

[naren]

Ok, hope together we will fix the issue. Thank you for your reply.

[Aleksander Nowakowski]

Hi, so some summary. There are 2 issues here. First one in our Eddystone firmware, v0.7. When the Button 1 is pressed and the beacon goes into Config Mode the adv packet contains an empty Service Data record. It should be filled with normal beacon slot data. Other issue is in Google Play Services 9.2.56. It crashes when Service Data are empty. This will be fixed in the next release. Hopefully it will also fix the permission issue. Please, try in couple of days. GPS usually updates automatically, so it should just start working, I hope.

[Roshan Rajaratnam]

Hi we have released a new version 2.0 of nRF Beacon for Eddystone with a fix for this. Please find the updated App on the play store and on GitHub. This is due to introduction of Project Delegation on the Proximity API and the app has been updated to support this. Let us know how it goes.