Pretty much what the title says.
There are tons of questions about this but the vast majority was only a matter of a missing HTTPS URL, a couple are due to misconfigured app restrictions, and the rest are unsolved.
I have no country or age restrictions in my app, I have both HTTP and an HTTPS URLs, I can see the page when logged in as a page admin and everything works fine, but when visiting the page while logged out, I don't see the tab.
Also, this is not a matter of clicking the tab and not having any content displayed, like in some other questions here. If I'm logged in with my The actual tab link is missing and if I copy the tab URL from when I'm logged in and then try to access it while logged out, I am simply redirected to the page.
I don't think it matters much but this is a tab that has been created via the Graph API. The Graph API docs don't mention anything about tab visibility, at least as far as I see.
This is driving me crazy, I've been at it for hours and can't find any solution or even a hint at what the problem might be.
Any ideas?
EDIT: All I described above is happening with our staging application, which has a self-signed SSL certificate. The live application, which has a "proper" SSL certificate, works just fine. Could the self-signed certificate be the cause of the problem?
Had the same issue this morning. Remove any audience restrictions from your app e.g 13 + or location as this means people have to login to see your app.
So it turns out it was stupidly simple: it was happening on our staging application but not on our live application because our live application uses a non-test FB app, while staging uses a test FB app, which is never seen by people who are not developers (or other staff) on that app.
Talk about wasted time...
Related
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.
We have a weird problem in that I have developed a mobile version of our website that just sits in a sub folder of the site e.g /mobile/page.asp (I know .asp classic don't blame me!)
I did want to create two domains one for the mobile site one for the normal site but I was told by our CTO to just do a sub folder.
However the problem is we want to be able to set a cookie that lets us know whether the user WANTS to be on the main site OR mobile site. They could in theory be on a desktop and still choose to go the mobile version (as we have links in the footer to switch views, e.g from the main site to the mobile site and vice versa).
However if someone comes to the site without a cookie set we do some user-agent sniffing do determine their device and then set a cookie before redirecting them to the right part of the site.
All our logic seemed correct however when we started testing it we started getting weird results.
On my iPhone 3gs it was working perfectly (most up to date OS) however on other peoples iPhones or Android phones people would
-clear cookies (at the beginning of the test)
-visit the site
-the agent sniff would redirect them to the mobile site
-but when they clicked on a further link on the mobile site the code took them back to the full site.
This didn't happen for me - also on our demo site it worked for some people and not for others - and also for someone on an Android device who downloaded FireFox it worked fine.
I and another developer who had the problem sat together and went through the steps one by one, doing the exact same thing, with debug on showing us what was going on.
However whilst I was getting a cookie set to "mobile" when I went to the mobile site he for some reason wasn't. It was like the cookie couldn't be set before a redirect even though the redirect was to the same domain.
I read some articles which said there was some issue in webkit with cookies and redirects which made me think this could be the issue on the iPhone Safari browser but that wouldn't explain why my 3Gs phone worked.
We have tried re-working the code but we need to be able to set cookies and do redirects in all cases. We even tried just changing the code that was setting a cookie to a session variable but even that didn't work.
I am really stuck and so is everyone else. We have spend days trying to debug it but cannot find a common denominator which would explain why it works on some devices but not others.
Can anyone help!!! Any advice would be much appreciated.
Thanks!
I am not sure if anyone has ran into the problem but it is really bugging me and affecting our uploading from our iPad to facebook.
I have a local server running XAMMP with a gallery of images displayed via a local web page. These images are from our Photobooths and automatically get added into the gallery when a photo is taken in the booth.
These can then be accessed on the local network via the iPad. Users can then login to facebook and share this images.
Because this is a shared iPad being used by multiple users, is there any way of getting users to login without having to answer security questions?? It used to be fine but now Facebook says the login is suspicious as it does to recognise the device.
I have created an App to post the photos to facebook through the Facebook Development site and it works perfectly from my account and many users, but some seem to get the suspicious login attempt and have to identify friends and date of birth etc.
Is there a correct way to do this?
Thank you Richard.
Is there a correct way to do this?
What you are experiencing is the “correct” way.
Facebook offers this as a security feature – a user can add his devices to his list of “known” devices, from which he will be able to login straight away, and have to answer additional security questions when logging in from a different, “unknown” device.
If users have this feature enabled, they should not be surprised by this happening in your scneario. It’s what they explicitly want, and they’re getting it.
So you should in no way try to mess with that, just because you might think this to be “uncool” or a “nuisance” – it’s not, it’s a feature offering extended security that the user wants and has explicitly chosen.
I'm working on an iframe style app that pulls the facebook optimized page available at http://store.starrco.com/?store_mode=facebook. I've done other, admittedly much simpler, iframe apps before without issue but though I've configured this one more or less the same when I try to view the canvas url it remains blank.
My settings can be seen here: http://www.abstraktmg.com/clients/starrco/starrcofbsettings.jpg
I've tried a few different permutations of this with the same results, this is the most complete setup though and most closely matches the settings template I was given.
This page is being generated by Webasyst's shop-script, which is specifically supposed to support this. The obvious answer then is to contact their support which I did, but after assuring them that my app settings matched their template, they said I needed to contact Facebook support and this is as close as I could find to any proper support system.
I checked both http and https versions of store.starrco.com/?store_mode=facebook and both worked outside of facebook.
However, there may be some framebusting code which might prevent the site from being loaded in an iframe. And I see that your settings appear to be missing the app domain entry.
I ran into the same problem, especially in Chrome and Firefox. The problem is, when the user is surfing with https on Facebook, the https Version of the iframe is called. But the browser do not show invalid certificate problems until you to right click page information.
You need to have a signed SSL cert by a CA trusted in the browser.
If the user has accepted it without the iframe - outside of Facebook, it works.
I have a Facebook app running in a Page Tab (the tab of a Facebook Page for an organization). The Page Tab URL (and Secure Page Tab URL) points to a URL on my own server which holds a PHP page that contains an iframe of a Google Calendar.
The app works perfectly fine when I open the Page using the admin account (both http and https). But when I open the Page using the user account of someone who has 'Liked' the Page, the app does not appear at all (both http and https). Any suggestions? Thank you.
Check if the app is in sandbox mode, in the Advanced section of the Settings here:
https://developers.facebook.com/apps
I believe that is the problem.
You may overlooked the "sandbox" setting that should be "disabled", this could be one explanation as per the answer above. If this have not answered to your question, than you may find another explanation here:
http://developers.facebook.com/docs/appcenter/guidelines/
Basically, if your application doesn't do anything it will probably not be approved and it will not be visible to nobody, except you - the developer. There are other issues, like copyrighted infringement and so on... please read.
(Also, just in case you are interested, it should be installed by more than 30 times, I guess different persons, in order to be "searchable").