We keep getting a white-screen on our FB application, although the server is successfully getting hit and no errors are occurring. Is there a setting or something we can do to resolve this? Does anyone know about this issue?
Browsing to http://m.facebook.com and turning on/off "Login approval" fixed it for me (https://www.facebook.com/settings?tab=security§ion=approvals&view).
Had the same thing and it turned out to be a Secure Browsing feature. Go to Account Settings, then click on Account Security and click the option for Secure Browsing (https) and all pages will load correctly.
Related
Hello I am trying to register for a facebook developer account.
But looks like the accept terms button is inactive.
Anyone knows what is the reason?
I have added the image also.
Solved!
I managed to register on Firefox.
I tried in Chrome incognito and it did not work.
You can't register unless you accept the Facebook Platform Policy and Facebook Privacy Policy. Basically, as WizKid mentioned, clicking on the toggle which right now says NO. Also, flagging your questions for being unrelated to code 100%.
Try using an incognito tab. I had the same issue on Chrome, but solved it by logging in from an incognito tab.
I have integrated facebook graph api is several applications but recently I have encountered a problem, while I have Secure Browsing enabled in my Facebook Profile -> Privacy Settings -> Security, and using simple FBGraphApi it passes all the steps of asking permissions and all but stucks on last step that is it doesn't get accesstoken in the redirect url set to http://www.facebook.com/connect/login_success.html where as as soon as I disable the Secure Browsing the login goes fine, and I get the accesstoken appended in the redirect uri.
The problem is Yes I am able to make it work, but it is impossible to tell all users to disable the Secure Browsing from their profile, and it won't bea good thing to do too..
Please give some thoughts on this, if any one encountered similar problem..
My problem is similar to this problem
We had the same problem with our application. A co-worker did some research and found that if you started the request process (oauth dialog in our case) using https:// instead of http:// then it would work with or without secure browsing enabled.
So
http://www.facebook.com/dialog/oauth/?response_type=token&display=page...
turned into
https://www.facebook.com/dialog/oauth/?response_type=token&display=page...
EDIT
There was also a redirect URL in the URL(s) above which he also changed to https
I am trying to post to user wall but I am receiving this error when when share window pops up:
The post's links must direct to the application's connect or canvas URL
Now, I made a proper Google search in hopes to find a solution, but the only one given was that I need to disable "Stream post URL security". I checked the advanced settings for my app and it is already set to disabled.
So, by having a few years of experience with development on Facebook, and by knowing how incredibly bad the communication between us developers and FB has been in the past, I'm highly doubtful that they will assist me on this. Although I have heard that feedback is better here on SO than the good old FB platform forums. Well, lets see if my only option is to set my hair on fire or that there might be a kind soul out there that can assist.
This answer from the WordPress forums via user Samuel Wood (Otto) worked for me:
Go to the Facebook App. Edit its settings. On the Advanced settings page, disable the "Stream post URL security" option.
Did you generate the access token using the Graph explorer app on FB?
Make sure you select your app from the select box on the top-right.
It will be selected as Graph Explorer by default.
This error happens as the selected app would be Graph explorer and its canvas/site url is not pointing to your site.
Doing this fixed my problem; it may fix yours as well.
With the new app interface, issue is solved by turning off the "Stream post URL security" in the "migration tab"
you always have to use the same domain for linking as specified on the app's developer settings. Now you can have several tlds, and custom prefixes as well.
For others experiencing this problem, I was able to resolve this by configuring the Facebook > App > Settings > App on Facebook > Canvas URL
Following a server move last week I have found that all the Facebook iframe apps I host are being redirect to http://www.facebook.com/4oh4.php
This is a straight redirection from the apps.facebook.com URL to the facebook 404 page - using httpFox. I can't see any request going to my server at all.
The funny thing is everything works fine when I'm using the app admin account on my PC.
I've check and the apps aren't in sandbox mode. It must be something to do with the server move. This was just a DNS update I didn't need to change any of the app settings.
Has anyone else seen anything like this before?
Thanks for the assistance.
This is usually an indication that your app is in "Sandbox"/dev mode. You need to take it out of Sandbox:
Go to https://developers.facebook.com/apps
Select your app and click "Edit Settings"
On the left hand side menu, under Settings, click "Advanced"
Under Sandbox mode, click "Disabled"
Scroll to the bottom and click "Save changes".
So, for whatever reason, some people can't see the custom facebook page tab. Not sure why, especially when I can see it just fine.
Link: http://on.fb.me/rKNxUS
Let me know if you need more info.
Do you have a https version of the page tab? If they're account always uses ssl and you don't you might run into issues. Other times I've seen resetting the app secret help with issues like this.
It shows a standard browser error page to me. "This webpage is not available Google Chrome's connection attempt to incontrolwebsites.com was rejected. The website may be down, or your network may not be properly configured."
May it be possible you didn't upload the webpage to the production server?
If it opens correctly from your machine: check that you don't have a custom DNS setting to point to your local webserver instead of the production server.