-
Notifications
You must be signed in to change notification settings - Fork 24
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
invalid_grant error #10
Comments
Hey @jeffkile! Unfortunately, I'm not really maintaining this repo much anymore. I built it for a company I used to work for, but now I don't even have access to an adwords account to test it. I need to put up deprecation warnings for it, I just haven't yet. As a side note, if you want to adopt this repo, lemme know and I can get the repo and npm permissions transferred to you. |
Hi @thereblerobot If you don't have time to handle this repo anymore. |
Hey @tonmanna! I'd be happy to add you to the repo for maintenance! I'll get those permissions to you once I'm at work (8a pt) As npm permissions are harder to sandbox, for the first couple releases you do, just ping me and I'll review/publish them for you, and if after a couple releases everything looks good I'll add you as an npm publisher. |
@tonmanna I've added you as a collaborator to this repo, feel free to add/delete/update the lib as needed, I would just say make sure you are writing tests, and don't force-push to master, work via branch/PR, and follow semver for versioning. Once you have a release ready, let me know, I'll review it and see about getting it released to npm. If after a couple releases everything is looking good, I'll add you as a publisher on npm and you can push new releases as you like. |
Hi @therebelrobot thanks for your sharing.What ever you're done before, We so appreciate and we will looking forward this repo until google they will have official NodeJS API. |
Whenever I try to make a connection I get an error
Unhandled rejection Error: invalid_grant
Does anyone know what this means and how I fix it?
The text was updated successfully, but these errors were encountered: