I am working on a project that needs a permission for user_link. Functionality that implements this feature is currently implemented on https://staging.meetmeinthe.bar/. I have fixed all of our bugs and made our app comply fully with the requirements. But, for some reason, one of FB reviewers keeps declining our submission, saying that our Login button does not work. We have tested our login functionality many times from multiple devices - it works. Why do we keep getting rejected? Any advices are welcome.
When you land on a web page, you should click orange "Login" button in the top-right corner to see it.
Thanks in advance for your time!
The solution was to contact support that verified the fact that everything was working correctly.
Related
I have my Facebook login process working on desktop and mobile, except for Facebook's inapp mobile browser (ios and now android). The issue is that if you call FB.login(), nothing at all happens. I assume this is because the inapp browser doesn't deal with popups.
I understand that a redirect auth flow circumvents the need for a login/permissions popup, however I have built a web-app, which means it is a pain to deal with storing the users current state at the point of signing in.
Does anyone have any good solutions for this?
Also I have tested many other sites login buttons through the inapp browser, and all of the ones I have tried so far don't work. Facebook has done a great job of breaking a large amount of sign up processes.
As stated in the comments, that seems to be a bug either in the Android FB- App or in the Android 5 WebView component. There is a bug report at facebook, but they are still working on it. The only solution i could find for now is to turn off the internal browser: http://www.androidpit.com/facebook-disable-browser
Because that action has to be taken by the user itself, it's no satisfying solution. Therefore i guess the only thing we can do at the moment is to stay tuned for facebooks fix.
Update
Facebook confirmed this is a bug. They are working on it. Stay tuned...
2nd Update
Facebook rolled out a patch. Works for me now.
I want to get approval for my app id only for the like and share buttons of facebook but it seems that it got more complicated then before.
When I go to my app then javascript sdk to create the code of javascript for my site it shows
This app is in Development Mode and not available publicly.
Modo público can be enabled in the App Dashboard.
So then I go to the app dashboard and it is asking a lot of information I don't have because it's only to have the like button in my site I don't want to read more likes of users.
So anyone can help me to find the right way to do this.
The only thing you should have to fill in to make the app public is the Contact Email on the main Settings page:
(source: infused.org)
Found this thread whilst having the same problem. In addition to infused's post, you have to go to "status and review" and turn "Do you want to make this app and all its live features available to the general public?" to Yes.
Furthermore, I noticed that removing the app id (as per the code you get if you are not logged in and go to the plugin generator page), then the code does not work at all.
Also, if the app is not set as live, then it will still sometimes work - just to make things harder to debug.
I have successfully integrated Paypal Embedded Chained Adaptive Payment system.
I have been testing it in sandbox environment. On GOOGLE Chrome, when user initiates the payment procedure, a light box gets opened with a login button inside it, but once user clicks on that login button, user comes across with following message
"Please continue with your purchase in the secure browser we launched. If you don't see it, click on Go."
The reason for this is that Chrome blocks the paypal login pop-up window. End user would not be able to figure out that what happened. Most of end users would not be aware about that paypal login pop-up window being blocked. Can we do something here so that we can avoid that pop-up window and can perform whole operation inside the Iframe only ?
Is there any solution this problem ?
Will it get resolved automatically once we shall move to production/live environment?
Please help me out.. We are going live very soon!!
I have been playing around with this a lot today and I too encountered the same issue with the lightbox. HOWEVER after much fiddling and time I decided to just try expType="mini" and it worked flawlessly. I did find one site that managed to get chrome to display the lightbox method correctly, but it was only successful about half of the time. It seems chrome is very sensitive to popups and sometimes it can be fooled and sometimes not.
Anyway the solution I found that worked was to scrap expType=lightbox and just go with expType=mini - seems to work without any problems. In the back of my mind I'm a little concerned that future browser releases (in particular chrome) will have updated popup blocking code may soon block this too. I hope this remains working, but I don't have a great deal of confidence in it. Make sure you have the good old Express Checkout method as a backup.
Hope this helped.
I have experienced problem accessing my Application Profile Page.
It was actually happening since today.
When I create a new application, in my Basic setting > View App Profile Page
it's just redirect to my website.
It also happening if I go to http://www.facebook.com/apps/application.php?id=228671190534769
However if I open another app (that is I have created before today). It works well
Anyone experiencing the same? Please help!
Yes... I am getting the same thing!!
Because of this error, I have raised a support ticket on Facebook Developers Support section. You can find this here: http://developers.facebook.com/bugs/208861915856389?browse=search_4ed6ed7d7170d5114488507
If this matches your experience, please ensure you click YES on the "Does this repro describe your issue?" at the bottom!
Came into the office today to do some more work on my nearly completed Facebook Connect website application.
And i have discovered for some reason, the "onlogin" event of the fb:login button FBML control is no longer getting fired!!?!
To anyone else that has a Facebook Connect FBML app (and using the JavaScript API for authentication), i would advise you test your application to make sure it's still working.
A friend of mine's app (which is live) has also stopped working as of today.
What's happening is you click on the "Connect to Facebook" button, it shows the FB login dialog, you log in.
Yes, they are being logged in to Facebook correctly (thankfully), but the "onlogin" callback event is not getting fired anymore, so the page just sits there (where before the "onlogin" event would redirect to the homepage, for example).
Of course if you refresh, you are logged into Facebook.
Seriously, WTF - what have those developers at Facebook done now?!?!.
Any ideas? Has anyone read any updates/threads on this issue?
UPDATE:
8 hours and still no fix in place. I've tried to do some workarounds (there is also an onclick event of the FBML Login Button), but it's all too early in the authentication cycle.
We need to be able to hook into a post-login callback to do things like redirects, permission popups, authentication logic, etc.
Nothing we can do without Facebook fixing this.
I just hope when i come in the office tomorrow this will be 'magically' fixed, much like this issue 'magically' appeared.
Well judging by the comments here i'm not alone. It's obvious at this point that Facebook have made a change somewhere, without telling us.
I just hope they rectify this issue ASAP as there is no workaround i can see for this.
UPDATE 2
Yep - (drum roll), its yet ANOTHER bug from that team of world-class developers at Facebook: (thanks Anon for finding link) http://bugs.developers.facebook.com/show_bug.cgi?id=11733
I love it how the comment from the FB guy Marc says "Only seems to be happening on old Facebook Javascript SDK", well, enable us to do server-side authentication with your Graph API (instead of just for retrieving user details/posting), and we wont have to use the old JavaScript API!
Fun and games.
FINAL UPDATE
Facebook have (seemingly) fixed this.
Let's hope it stays fixed.
Given the 'correct' answer to Anon (as he found the link).
Please confirm and vote on this bug... this should be fixed asap!!
http://bugs.developers.facebook.com/show_bug.cgi?id=11733
if in FB.getLoginStatus you are passing second parameter as true, pls make it to false.
I resolved callback issue using this trick.
Thx
This is a bug and they are about to fix it