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.

[Aleksander Nowakowski]

Hi,

The SHA1 has to be generated from the key you use to sign your app. When compiling from Android Studio you use a debug key (/user/.android/debug.keystore) (password 'android'). For production release use your production key. You can read how to do that on Proximity API documentation online. Also, make sure you have replaced all he keys in the app to those from Proximity API console.

[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.