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
Sorry for all the issues! I am enjoying using your app.
I noticed when playing with the new token refresh feature in 4.0.0 that when the token is expired, a new token is requested from Yahoo and supplied to the callback function, but the original request to the API is not remade with the new token.
Is there a way configure it so that the original request is remade upon a successful refresh of the access token?
The text was updated successfully, but these errors were encountered:
This is a bit convoluted as this lives inside of a catchall route so it can execute any request -- but I think it's what you're looking for.
Basically, I'm using a callback function and you can see on line 70 that if it errors I am refreshing the token and then re-submitting the request. This same workflow MIGHT actually live somewhere in the history of the new sandbox / docs site https://github.com/whatadewitt/fantasy-docs-next/blob/master/pages/api/yahoo/%5B%5B...slug%5D%5D.js as well, but I don't have time to search through it right now.
Again, sorry for the delayed response! Hope I am not too late!
Sorry for all the issues! I am enjoying using your app.
I noticed when playing with the new token refresh feature in 4.0.0 that when the token is expired, a new token is requested from Yahoo and supplied to the callback function, but the original request to the API is not remade with the new token.
Is there a way configure it so that the original request is remade upon a successful refresh of the access token?
The text was updated successfully, but these errors were encountered: