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.
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.
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, 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?