-
Notifications
You must be signed in to change notification settings - Fork 49
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
More of a question about InstagramAPI._credentials #4
Comments
I’m thinking you’re right about the params check @chiefy. I'll get that added — thanks for the heads up. D |
did this get added? I'm getting the same issue now... |
I believe I did @joemccann, but this might be related to #6, which is in the works. I’ll check while there. |
I fixed it...i'll submit a pull request |
joemccann
added a commit
to joemccann/instagram-node-lib
that referenced
this issue
Aug 20, 2012
Wonderful, please do. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First off: thanks for your work on this, I am messing around w/ Instagram for fun right now, but have a few ideas for an app I want to develop.
I was kind of confused by the documentation. So I have my script (using express) logging in and getting a valid access_token. In my Instagram.oauth.ask_for_access_token callback I am setting the access_token as:
Then when I try to call Instagram.users.self() without any parameters, I get an error. I looked through the code and it looks like it should be defaulting to Instagram_config["access_token"] but it doesn't get that far - it gets to:
(sorry, compiled - I'm not so much into CS yet)
And it dies on that line - here's the trace:
I am not sure if this is by design, but later you're checking for this._config['access_token'] so maybe a check if params === undefined is needed?
Anyhow, thanks again for your work.
The text was updated successfully, but these errors were encountered: