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.
Related
So I've seen many related questions but they all date from years ago (Facebook SDK changes constantly) and mine is more specific.
I'm building a web app which requires authentication and Facebook API is one of its auth solutions and I'm trying to catch some scenarios. So as I asked earlier, what happens when someone removes my app from Facebook via the "Apps and websites" settings and tries to reconnect in my app ?
It might seem obvious to some that the user wouldn't get logged in because as far as I know in 2021, FB SDK uses an app specific ID for each user which gets generated when logging in for the first time and is useless when the user removes the app from his settings because there's no more mapping between the ID and the user.
But I've experienced in an app that I used (ometv kinda similar to omegle) that they log you in even after you delete them from the Facebook settings.
Thanks for considering my question.
EDIT: This is the edge case that I'm referring to from facebook dev
Someone removes your app from Facebook via app settings and revisits your app. Your app should detect this and prompt the person
to log back in. Go to your app and tap on the "Log in with Facebook”
button Tap OK to accept the read permissions (and OK again to accept
write permissions where applicable) Go to app settings on Facebook and
remove your app Repeat steps 1-2 and verify that Facebook Login works
A more specific question that I might ask would be whether or not a user can bypass this behavior ?
I am using parse facebook login for new users of my app. Most users are able to use it without a problem and I have successfully tested all Facebook login scenarios. Some users, however, report that when they press the login button they see brief activity indicator and then nothing happens. In code, no error is registered but the user is not brought beyond the login page to the app's initial screen. The problem resolved if the user deletes the app from their Facebook app settings and then tries again. Has anyone else experienced this and/or found a solution? Thanks
Not sure if this ever got resolved for you.
There are multiple possible causes for this of course including your own code. However, we've seen a similar issue with 2 causes / solutions.
UX-wise we detect multiple failed logins (typically with no error code) and then pop a notification telling the user how to solve. Still digging for a code-level solution that'll solve either of these issues permanently (if you found one, please post!) but hope these help & let you know you're not crazy.
Issue #1: User is logged into multiple Facebook accounts from the same device (e.g. a primary account and an org or 2ndary account).
Fix #1: Have user log out of all Facebook instances (app, safari, iOS settings) and then log back in.
Issue #2: User has rejected Facebook permissions.
Fix #2: For iOS, make sure Your App is toggled on in Settings -> Facebook -> Your App
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.
Today, on my Facebook app, links appear to be broken. Everytime you click a link (to another page of the application, not external), Facebook returns the user to the login prompt, even if the user has already logged in.. I usually use relative urls, but if I set absolute, the link doesn't work too, but in this case the page doesn't change...
Anyone having same problems? Any ideas? I just can't find solutions..
Edit: for "Facebook app" I mean an iframe application that runs on Facebook site, not the Facebook application for a mobile device
Solved :) The problem was I used on old versione of the PHP SDK. I've updated the SDK with the latest version and also the Login part of the code; now it's ok. Thanks all for your help ;)
Did you tried to reinstall the Facebook app? Also if you use Android you can delete the cache on your phone.
Everytime you click a link (to another page of the application, not external), Facebook returns the user to the login prompt, even if the user has already logged in..
Do you have Authenticated Referrals turned on for your app?
Otherwise, you must be triggering login yourself somewhere in your app. If so, check the conditions under which you are doing so, and if your app recognizes a logged in user correctly, or if maybe there is some kind of cookie problem.
If that doesn’t help you to figure it out on your own, please update your question with relevant code.
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.