-
Notifications
You must be signed in to change notification settings - Fork 180
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
Authentication broken? "Invalid access credentials have been reset" #6
Comments
does it happen immediately or after an hour or so? |
Immediately. |
yowza -- i just tried the same thing and i got a segfault. stacktrace:
i'll try and look into this soon ... @hadley, does it work for you? |
Same issue here
|
I'm in the middle of an OAuth 2.0 overhaul in httr - once that's done, I'll take a look at this. I think it should be a relatively straightforward fix. |
Same issue for me. |
For anyone else who ran into this issue: I didn't bother trying to dig out the original cause, but I have another pull request out that makes everything work nicely with the new version of |
Dear hadley,
I am trying reproduce the example in the README.md with a dataset of mine, but authentication first completes succesfully and then fails because of a "Invalid access credentials have been reset" error. This happens with both Google's sample data and mine.
Any hints? Thanks!
Giacecco
The text was updated successfully, but these errors were encountered: