-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How is the refresh token used? #4
Comments
I just went through |
@JonasGessner , appreciate if you could share some code snippets I have the same question here.
|
As I said in my last comment you don't have to refresh your access token manually. It's all handled automatically by the |
One more question What I have done here is:
Step2: when you come back and launch the app days/weeks later, you still can get authorization via
. So i can get the token again via : _authorization.authState.lastTokenResponse.accessToken, However I can not make sure myself whether this token is valid or not. My question is: when and where to set "set the stateChangeDelegate of the authState of your authorization object" Thanks |
Finally, i got the answer myself.
This thread tells everything: https://github.com/google/google-api-objectivec-client-for-rest/issues/75 |
I faced same problem. I important thing, i think, we should get accessToken by |
The way I understood this guide is that you receive a refresh token and an access token. The access token is only valid for a limited time and when it expires you have to use the refresh token to get a new access token (instead of requiring the user to sign in again). How is this handled in this library and in combination with the Google API Objective-C library? The readme doesn't mention any token refresh request. Any clarification would be appreciated :)
The text was updated successfully, but these errors were encountered: