React Native Facebook Login Error: 'There is an error in logging you into this application'

[riya-coddle]

I'm encountering an issue with Facebook login in my React Native project. I've implemented Facebook login using react-native-fbsdk-next v^12.1.0, and while it works perfectly through the web app, I'm facing an error when the Facebook app is installed on the device.

The error message I'm receiving is: "Login Error: There is an error in logging you into this application. Please try again later."

Has anyone else encountered this issue? If so, could you please share any insights or solutions you've found? Any help or guidance would be greatly appreciated.

[MiteshIts]

Same But got solution

keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore | openssl sha1 -binary | openssl base64

keytool -exportcert -alias androiddebugkey -keystore "C:\Users\USERNAME.android\debug.keystore" | "PATH_TO_OPENSSL_LIBRARY\bin\openssl" sha1 -binary | "PATH_TO_OPENSSL_LIBRARY\bin\openssl" base64

keytool -exportcert -alias YOUR_RELEASE_KEY_ALIAS -keystore YOUR_RELEASE_KEY_PATH | openssl sha1 -binary | openssl base64

added in hashkey of Facebook

[short-dsb]

This affects Android logins when the Facebook app is installed, and typically means the appropriate certificate hash hasn’t been saved to your Facebook app.

You can follow the instructions here to generate and save the hash from your signing certificate.

Note that if Google is signing your releases, you’ll need to get the SHA-1 from the Release > App signing > App signing key certificate in the Play Console and run this command:

echo YOUR_SHA1_HERE | xxd -r -p | openssl base64

If you’re also using App Tester for internal releases, you’ll need to run the same command for the SHA-1 from Release > Internal app sharing > Internal test certificate and save that hash as well.

Hope this helps!

[risbellycarvajal]

I'm facing the same issue in our app, there are specific users from android that are unable to log in from the Facebook app (the need to uninstall the app and log in from the device browser)

Any progress or recommendation for this issue?

[janeirojoaopedro]

Hi, I was facing the same issue beacuse I was type the wrong password on step 2. Definitely @short-dsb and @MiteshIts solutions worked for me, from this documentation (for mac OS in my case)

1. keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore | openssl sha1 -binary | openssl base64
2. keytool -exportcert -alias YOUR_RELEASE_KEY_ALIAS -keystore YOUR_RELEASE_KEY_PATH | openssl sha1 -binary | openssl base64

On step 2, even with a wrong password this generate a key, so be carefull when you do that. To be sure what the YOUR_RELEASE_KEY_ALIAS, YOUR_RELEASE_KEY_PATH and password are, you can go to android studio > build > generate signed bundle or APK > App bundle or APK > and then you can copy the key store path and alias. The key store password, I suggest to type it to and test generate an APK/AAB be sure if it is right, if it is wrong the bundle generation will fail, but that way you will be sure what the password is. Hope it can help you.

[mikehardy]

Looks like a solved issue, great collaboration. If there's something missing in the documentation here that would point people to the solution during initial configuration, anyone can propose a PR to the docs, might help folks in the future