I taken the Android-nRF-Beacon-for-Eddystone app code from github.
From my account I configured my Google Dev console:
-
enabled proximity API
-
added credentials for OAuth2.0 and Client ID. Based on the SHA1 code of my machine.
I taken the Android-nRF-Beacon-for-Eddystone app code from github.
From my account I configured my Google Dev console:
enabled proximity API
added credentials for OAuth2.0 and Client ID. Based on the SHA1 code of my machine.
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.
Also, make sure your app asks for the permission before registering a beacon. This may be your problem, as you get 403, not invalid key error. Double check it. Maybe there you also have to change something?
Also, the app is using Google's URL shortener API from where you also need the APK KEY. Put it in the manifest file as well.
I downloaded the app nRF Beacon for Eddystone from google play store, Trying to register my Beacon, I am facing similar issue.
What phone/Android version are you testing? I have here a Nexus 6P with Android N preview 4 and Google Play Services are crushing every time I try to connect to GPS. Then I'm getting 403 as well. It successfully asked me for a permission for URL Shortener API but never for Proximity API.