-
Notifications
You must be signed in to change notification settings - Fork 187
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
OAuthToken not being set after getAccessToken() success. #21
Comments
Are you using
We'll consider to add this automatically to |
Hah, I'm currently just doing |
Please, warn in the README that using 'http' with default OAuthTokenProvider configuration would lead to have token undefined. In a previous attempt to use the library, I gave up using it because of this. In this attempt I fortunately read this issue! Thanks! |
@nicogarcia Thanks for reporting your issue. I created an issue to fix this in a more clever way. I'll probably be able to fix this next week. |
up |
Thanks goodness for this issue. I encountered exact same issue. |
Hi, I'm doing
OAuth.getAccessToken(credentials)
and getting a successful hit on the server. The token is coming back fine, nothing wrong with request cycle. The issue happens when I callOAuth.isAuthenticated()
aftergetAccessToken()
runs, it always returns false. I stepped through the code and have a screenshot below. It looks like theOAuthToken.token
is still undefined even after being set directly when the request comes back successful. I have theresponse.data
on the right side and the breakpoint set right after the token should be set. Any help would be appreciated :)The text was updated successfully, but these errors were encountered: