Skip to content
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

You do not have permission to open this page. fbconnect://success/#access_token #45

Closed
kanelbulle opened this issue Jun 25, 2010 · 5 comments

Comments

@kanelbulle
Copy link

Hi

I've been trying to get the latest version of the facebook SDK to work but I get this behaviour:

When initiating Facebook.authenticate() the facebook dialog pops up blank but with a loading dialog on top. After a second or two I get thrown to Browser where a url fbconnect://success/#access_token=blabla has been loaded and the page says "You do not have permission to open this page. fbconnect://success/#access_token...."

Why does this happen? If I clear my cookies first I'm prompted (through Browser) for username and password at touch.facebook.com, and then the same page as above is shown.

I've monitored the console output and there is a bunch of really long urls (some more than 1200 characters long) being passed to the Facebook-Webview, a bit strange.

I've tried migrating to the new permissions in the facebook app we're connecting to but this did not change anything.

Is there anything I've missed here?

@oleksandr-semenov
Copy link

no. it seems to be the same problem as http://developers.facebook.com/blog/post/392

@soneff
Copy link

soneff commented Jun 25, 2010

Try pulling the latest version of the code and let me know if the problem still exists: I will try to repro.

@kanelbulle
Copy link
Author

I pulled the latest from repo and it now seem to work! Were there any changes made to the latest in repo in the last few hours?

Thanks a bunch!

@daen
Copy link

daen commented Jun 25, 2010

yes, I also have this issue.
but when I download the latest version. I found this bug have fixed.

@soneff
Copy link

soneff commented Jun 25, 2010

Yes, this bug was caused by a server-side change that needed a corresponding change in the client code. I've asked server-side engineering team to avoid this in the future.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants