android - New Google Sign-In: Token used too late, 1452928807 > 1452897485 -


i'm trying implement new google sign-in in new app.

i implemented official example additionally requesting idtoken.

then send token server via volley post request , verify using python example google posted here (on bottom of page).

everything working fine except verification of idtoken. following error occurs time:

token used late, 1452928807 > 1452897485:

it followed account information of user.

it seems token not refreshing - or - because expiring date of token stays same, if sign out , in again.

google doesn't mention method refresh token or if has expired.

has how solve problem?

 1452928807  1/15/2016, 11:20:07 pm gmt-8:00  1452897485 1/15/2016, 2:38:05 pm gmt-8:00  1452928807 > 1452897485: 

probably timezone mismatch.

id token expires in 1hr. looks it's issued @ 1:38pm (expire @2:38pm) , used @ 2:20pm? (all in gmt-8) (i don't know why took hour try verify it? :) retrying?) guess in gmt+1 time zone?

could confirm server's time / timezone settings , paste python code used? server sdk version?


Comments

Popular posts from this blog

get url and add instance to a model with prefilled foreign key :django admin -

css - Make div keyboard-scrollable in jQuery Mobile? -

ruby on rails - Seeing duplicate requests handled with Unicorn -