when you visit a Facebook Canvas app (such as http://apps.facebook.com/branchout/) and you are not logged in to Facebook, you will get the "Please log in to continue." dialog every 10 seconds or so.
I am planning to develop a Facebook Canvas app that does not ask for user authentication/ app authorization upfront (I don't want to scare users away), but I do not want to go that way if I cannot stop that dialog.
Is there any way to disable it, or should I rather ask for authentication/ authorization upfront? Thank you for sharing your experience.
Brent is right, it's just a bug. The what's-going-on pane on the right hand side tries to reload, and gets confused when there's no user logged in. Don't worry about it, it should be gone soon :-)
I'm pretty sure that is Facebook trying to refresh their ads. I've done a few apps that don't require authentication or login until specific actions are performed. If you are not logged into Facebook, then that prompt comes up. The only action I am performing is calling getLoginStatus on load. Unfortunately, it doesn't seem like there is any way around it. When I load my app directly (not in a Facebook iframe), the prompt doesn't come up.
Related
I have made website where people can logon to with Facebook.
Ik keep getting this message every time I submit my request.
Your app's Facebook Login button does not work. Please make sure the
provided test user can successfully and consistently log in with the
Facebook Login button. See more about authentication.
Even though my created test user can login with IE, FF and Chrome.
Can anybody help me?
I am getting the same thing. I think you need to put the facebook javascript code in your website for them to see. I think that it is a bot reviewing your app, not a person, and it does not see it.
When a user is not logged in and they navigate to a page tab made with our app, they get an obtrusive dialog asking them to log in:
This has nothing to do with http vs https, the app is not in sandbox mode, there is nothing in the tab asking for a login or user information, etc. I've gone through the app settings at least a half dozen times now, and nothing is wrong there. Aside of urls, the settings are identical to another app I have that does not suffer from this problem. I'm stumped!
Edit: here is an affected tab: https://www.facebook.com/StaticHtmlThunderpenny/app_203351739677351
This message is not about login to your app, but Facebook in general.
So my guess would be that the page your app is installed as page tab app on is restricted in some way – by age, location, or for having alcohol-related content. And then of course Facebook asks for login, because otherwise they can not determine whether or not the (as of now still “anonymous”) user qualifies to see the page.
So go check the page settings.
This is actually not app related question.
This is thumb rule!! To access any app on Facebook, you need to log in to Facebook. You can see Facebook page without log in. But for facebook apps, you should be authentic user.
with this issue in my own experience that I came across some years back with a facebook app that I was running, if this doesn't relate to any of your other social networking apps then am aligning two set of possibilities and solution.
The user might have not properly logged out as "written" in the app for the users logout stage.
Solution would be that the user logout as expected before closing the app.
The user might have set up an automatic login prompt which was removed by the app when it was been updated automatically. (If you do get me???)
Solution would be to monitise your app on updates and login informations or better still just login and logout ask intended by the app and for security reasons.
Lastly I would say that automatic bookmark database should be added to the server part so current pages as the user uses the app would be saved after logout or login stage. Thank you, hope this helps and if not let me know what am missing.
I'm building a public installation using an iPad, built as an iOS web app (using the "Add to Home Screen" functionality) which is going to allow users to share content on Facebook.
I'm currently logging the user in to Facebook and getting them to authorize my Facebook app when they click my custom share button. On a successful login, I open Facebook's Feed dialog and allow them to share. Once they have shared (or clicked cancel) I automatically log them out, making sure that the next user that uses the public installation won't be able to share to the previous user's Facebook account.
This all works well, but things get tricky if someone was to hit my custom share button, log in to Facebook and then not allow my app. This would mean that they have logged in, but as they haven't authorized the app, I don't have an access token, and so can't log them out (FB.logout() requires an access token).
Is there a way around this?
Or is there another way that I can log a user out?
Or is there a safe way to allow a user of a public installation (built in HTML) to share on Facebook and be automatically logged out afterwards? Would building a native obj-c app, and using Facebook's iOS SDK help?
The best I can think of is that if the user logs in but doesn't allow the application, they are told that they need to log out, and redirected to Facebook to be able to do this. However this offers them the chance to browse Facebook and (through shared links in their feed) the whole Internet - this isn't acceptable for our installation.
I solved this problem by creating a native iOS app, where the Facebook share link opened in it's own UIWebView. And once the sharing was complete, I deleted all session & cookie information, effectively logging the user out.
I have a website that's working with Facebook Connect (or Facebook for Websites as I think it's called now). When a user first comes to the site he's able ot browse around and do some simple things without any integration with Facebook. If he wants to perform some advanced operations, we need him logged into Facebook and to authorize our app to grab some very basic information about him. We're trying to be good corporate citizens by letting him get a taste of the site without forcing him to be logged in and authorize.
To do this, we have a Login button that he needs to push before performing advanced functions. When it's pushed we call https://www.facebook.com/dialog/oauth, etc. to get things set up.
This system works fine except for one thing. IF he is already logged into Facebook AND IF he has already authorized our app, he should just be frictionlessly logged in when he goes to the webapp. But, I can't see how to do this.
Sure, I can call https://www.facebook.com/dialog/oauth when he starts the webapp, and if the conditions are right, things work great. But if the conditions aren't right, then he's presented with a bunch of things to do that I don't want to task him with just yet.
Surely there's a way around this. How can I frictionlessly allow my users to authenticate through Facebook with the stipulation that if any of the conditions are wrong, just abort the whole process without showing the user anything?
Before you display a login button for the user, call FB.getLoginStatus() to see if they're already logged in or not.
Whenever I first click on a Facebook app it puts up a screen asking for permissions. Does the API enforce this, or is it possible to display a screen using either fake or the user's publicly accessible data?
You do not have to ask for any permissions right away. Your app can have the equivalent of a "guest" mode, similar to how many websites work until the user has logged in. I'm not sure why more apps don't operate like that, as a user I'm always a bit put off when something asks for permission before I've even seen the first page of it.