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