- Community
- Question
I am building a hybrid app that is just using the share dialogs for Android and iOS.
iOS is working great and Android is also working great IF the facebook app is installed. On this emulator, it is not and I get an error when I try to log in to use the share dialog.
"For your account security, logging into Facebook from an embedded browser is disabled"
I am using SDK version 9. I am using a relatively old simulator to make sure we have good compatibility. I have enabled embedded logins from our business app dashboard. Can anyone tell me what's going on here and how to allow it?
To be clear, it is definitely opening an embedded browser to do the login. I just have no idea why it would be blocking the login
Using a facebook generated user worked
Can you share what did you do to allow the user to login? I'm getting the same error
I just got a test user from facebook in the business dashboard. I still don't have it working with a real user
have the same problem. Any progress?
I got the same issue, but not happened on every device, from now on, iphone8 ios14.6 is blocked from facebook embed login on app webview
I am having the same issue but not with devices, with accounts. Some accounts are blocked while others work on same device.
We've received many reports from users experiencing this issue, and I can consistently reproduce this with my personal Instagram account, linked to my personal Facebook account.
Anyone seeing this, please use the Same Here button on this bug: https://developers.facebook.com/support/bugs/2877958252518195/?join_id=f11bcd07c86b6
Not sure if you have seen this post yet. Looks like it will not be supported as soon as August: https://developers.facebook.com/blog/post/2021/06/28/deprecating-support-fb-login-authentication-android-embedded-browsers/
[...]
[...]
991394
Trying to implement a Meetup API login, having the same issue
I've updated to 15.2.0 and it's partially solved. Here's what would happen after upgrading: 1. If I'm not logged in to FB app, it works fine. From my app, if I login via Facebook, it will show new modern UI 2. If I'm logged in to FB app, then switch to a page profile, go back to my app, login via Facebook, it will show the old webview UI. It'll show error message "For Your Account Security Logging Into From An Embedded Browser Is Disabled" after I enter FB email/password. If I log out from FB app, login again, it'll work.
So the key thing with the new SDK version is that if you have ever switch to a page profile on your FB app, it won't let you login via FB unless you logout on your FB app. This page profile thing was introduced recently https://www.facebook.com/help/123930246348340
How do I resolve this?
Hi Adrian, I've posted an answer myself, which contains information it's not going to be fixed sadly enough.
Login disabled For your account security, logging in to Facebook from an embedded browser is disabled. To continue, download and log in to the Facebook app on your device and try again.
For those who have missed it, this function has been removed due too security. Hope this answer helps you out, even though it does not contain a fix.
Deprecating support for FB Login authentication on Android embedded browsers https://developers.facebook.com/blog/post/2021/06/28/deprecating-support-fb-login-authentication-android-embedded-browsers/
Yes, I just saw. Its working with a test user but not on production
What is the actual restriction date of this policy?
Beginning of august, see the linked article. So it's already deprecated
How did you solve this issue?
I dont think he did - he says he used a test user to test and it worked. But I get the same error and can't login with a real user in production so...
Geoffrey, I hate to ask you to do this, but can you pull your answer? It makes it look like there is an answer when there really isn't. No hard feelings, I'm just desperate to get this answered
Hello Christopher, sorry to mislead you about my post, I'm also desperate to get answer for this problem. FB is not responsive in this issue. :(
Hi Christopher, I've posted an answer myself, which contains information it's not going to be fixed sadly enough.