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
Error connecting to graph.facebook #37
Comments
See the Readme file in the main page, you need to write your app_id in the code. : I get a ''missing client_id'' error. ; Read the setup instructions and make sure your application ID is set. |
Yes, you are right about the app_id. |
Just checkout a copy, and fill in the appid in DemoAppViewController.m line 23. Did not see the issue you mentioned. |
Sure. I just checked out the code today. After running a git diff HEAD, I dont find any changes, except from my static kAppId NSString, and the fact that I'm using SImulator 3.2 instead of 4.0. Anyhow, it doesn;t seem obvious to me what is going wrong. Can it be the callback URL for my facebook app? It is just very weird. |
Yujuan, Thanks so much for your quick replies! I had to delete and get the code via git again. It now seems to connect fine! Thanks |
Hi there,
I haven't thoroughly delved into the code yet, but looks like whenever I run both the examples, I get the same json object-error from facebook: "error": {
"type": "OAuthInvalidClientException",
"message": "Missing client_id parameter."
}
Somehow, the login params are not passed in the main URL (https://graph.facebook.com/oauth/authorize). Is there a quick fix to alleviate the problem? I checked out the latest code from your git repo, but has this bug... I also used the kAppId of a sample facebook app that I created a week ago, but like I said, the params in FBLoginDialog::initWithURL are not passed in the URL. I'll continue debugging your library, but I was wondering if you have a quick fix.
Also, the UnitTesting code breaks, because it doesn't find the main application's window at launch-time (it's null).
Thanks so much!
Fotios
The text was updated successfully, but these errors were encountered: