Android nrF beacon for Eddystone

RE: Android nrF beacon for Eddystone

Roshan Rajaratnam — Fri, 21 Sep 2018 08:39:53 GMT

Hi, nice catch yes we did use a web application client id at the time as there was something wrong while trying to use the Android OAuth client id. But haven't gotten around to check if it does now.

RE: Android nrF beacon for Eddystone

Tom Howard — Wed, 19 Sep 2018 13:08:49 GMT

Thanks for your response. Would it be possible to confirm that this is an OAuth client ID for Android rather than and OAuth client id for web application? If this is not the case then what is the use case for the OAuth client id for web application that the android nrF beacon suggests to create.

RE: Android nrF beacon for Eddystone

Roshan Rajaratnam — Wed, 19 Sep 2018 13:00:42 GMT

Hi, in this case yes, it's authorized against google's authorisation server. Client ID is something you create on the console, and is used when authorozing a user. Once authorized you get an access token and a refresh token. Use the access token to access the proximity beacon api. When your access token expires use the refresh token to get a new one. You will find more information here developers.google.com/.../OAuth2