Note that there are some explanatory texts on larger screens.

plurals
  1. POGoogleAuthUtil and PlusClient
    primarykey
    data
    text
    <p>According to <a href="https://gist.github.com/ianbarber/5170508" rel="nofollow">https://gist.github.com/ianbarber/5170508</a> you should connect with PlusClient and only then get token with GoogleAuthUtil.</p> <p>But in my application i have backward scenario: i've already obtained token via GoogleAuthUtil.getToken(app, email, GOOGLE_AUTH_SCOPE). And when i'm trying to use PlusClient two things happen:</p> <ol> <li>setAccountName has no valuable effect(except it throws exception when wrong account set) because account chooser dialog will still be shown</li> <li>User have to login second time(accept application)</li> </ol> <p>Actually, the all i want is to retrieve basic user information like user profile icon and name having his email and token from GoogleAuthUtil.</p> <p><strong>P.S.</strong> Yep, there is <a href="http://developer.android.com/guide/topics/providers/contacts-provider.html#UserProfile" rel="nofollow">http://developer.android.com/guide/topics/providers/contacts-provider.html#UserProfile</a> but it's usable with API 14 only</p> <p><strong>Update</strong></p> <p>I still have no idea how GoogleAuthUtil and PlusClient connected and how to force them to work together. The only working solution(found in GMS samples) is to fetch <a href="https://www.googleapis.com/oauth2/v1/userinfo?access_token=token" rel="nofollow">https://www.googleapis.com/oauth2/v1/userinfo?access_token=token</a></p> <p>But it's quite weird - you have 600KB library classes + Google Play Service app installed on device and you still have to fetch user profile by hand...</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload