This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

register beacon return 403, permission_denied error

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.

Parents
  • 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.

  • This is a respond I got from the author of nRF Beacon for Eddystone app:

    Hi Naren, few steps for you to follow up. Check if you application ID and the package name are the same. Also it would be really helpful for you to start with a debug key before a release key.

    1. Get the sha1 from the debug key
    2. Register it on the developer console along with your package name.
    3. copy paste the API key on you getyour manifest file where it's mentioned on the manifest file obtained from our example ongit hub
    4. Create OAuth client ID And make sure you ask for permission using OAuth before registering a beacon.
Reply
  • This is a respond I got from the author of nRF Beacon for Eddystone app:

    Hi Naren, few steps for you to follow up. Check if you application ID and the package name are the same. Also it would be really helpful for you to start with a debug key before a release key.

    1. Get the sha1 from the debug key
    2. Register it on the developer console along with your package name.
    3. copy paste the API key on you getyour manifest file where it's mentioned on the manifest file obtained from our example ongit hub
    4. Create OAuth client ID And make sure you ask for permission using OAuth before registering a beacon.
Children
No Data
Related