You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cached tokens do not expire and are used after their expiration. This leads to an error being thrown, and the API request failing.
For example, I make a request at 11am, and a token is generated with a (default) 1 hour expiration. I then make another request at 2pm, and an expired token is used to make the request.
I realize I can clear the tokens, but a simple one liner can check for expiry.
The text was updated successfully, but these errors were encountered:
Yes in deed, token expires but it isn't checked if it expired so new token is not generated. I know about it and I'm planing to fix it. For now I suggest generating token on every request or just do manual check. I will notify you when I fix it.
Hello, I'm using your packages to request Google Calendar API. I make sure everything work fine before. But in now, it's only work in localhost. In deployment server, it's always return "Invalid Credential". I think my issues relate to the expiration token. Can you suggest any idea to resolved this issues? Thanks!
I've published a new version that fixes tokens expiration issue. Please test it out for me, because I haven't made test for this package. Let me know if everything works.
Cached tokens do not expire and are used after their expiration. This leads to an error being thrown, and the API request failing.
For example, I make a request at 11am, and a token is generated with a (default) 1 hour expiration. I then make another request at 2pm, and an expired token is used to make the request.
I realize I can clear the tokens, but a simple one liner can check for expiry.
The text was updated successfully, but these errors were encountered: