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]

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.