• Register
0 votes
861 views

Problem :

I am getting following error
login error: there is an error in logging you into this application. please try again later.
6.9k points

2 Answers

0 votes

Solution :

The error your facing because of invalid hash key.

You can create the Hash key using the following command and after that you need to update the same at https://developers.facebook.com/ under Settings-> Basic -> Android HashKeys

e.g.
keytool -exportcert -alias ADD_RELEASE_KEY_ALIASE_HERE -keystore ADD_UR_KEYSTORE_PATH_HERE | openssl sha1 -binary | openssl base64

Now you can find the Release Keys Alias of your keystore using the following command:

keytool -list -keystore ADD_UR_KEYSTORE_PATH_HERE

I have also experienced the issue by using the above HashKey the login works fine if I have installed the release APK directly to the device, But if I upload the APK to Play Store and after that try to install the app from store then it shows the same Login failed error as shown earlier. The solution for this issue is as follows:

  1. Go to Release Management at https://play.google.com/apps/publish/signup/
  2. Please select Release Management
 -> App Signing
  3. Now you can see the SHA1 key in hex format App signing certificate.

  4. Copy the SHA1 in the hex format and convert it in to the base64 format now you can use this http://tomeko.net/online_tools/hex_to_base64.php to do that without the SHA1: part of the hex.

  5. Finally go to Facebook developer console and add the key(after convert to base 64) in the settings —> basic –> key hashes.
And your issue is resolved.
36.1k points
0 votes

Solution:

The error happens since of invalid hash key.

We can make Hash key emplying the below command and update the similar here under Settings-> Basic -> Android HashKeys

keytool -exportcert -alias ADD_RELEASE_KEY_ALIASE_HERE -keystore ADD_UR_KEYSTORE_PATH_HERE | openssl sha1 -binary | openssl base64

You can trace the Relase Key Alias of your keystore employing the below command if required:

keytool -list -keystore ADD_UR_KEYSTORE_PATH_HERE

I have also experience an problem like by employing the above HashKey the login performs fine in case I install the release APK directly to the device, however when I upload the APK to Play Store and install app from store then it displays the same Login failed error. The solve for this  issue is as follows:

  1. Go to Release Management 

  2. Choose Release Management
 -> App Signing

  3. You can view SHA1 key in hex format App signing certificate.


  4. Copy the SHA1 in hex format and change it in to base64 format, you can exercise this link do that without the SHA1: part of the hex.


  5. Go to Facebook developer console and include the key(after convert to base 64) in the settings —> basic –> key hashes.

Only throwing this out there for people still experiencing this problem. The hash I made through the keytool was somehow incorrect. I solved it by doing the following:

In case you meanwhile uploaded your app to the playstore and enabled "app signing by Google Play" there is a solution (at least this performed for me):

  1. login into you play console

  2. click on the app

  3. Currently, on the left side click "release management"

  4. click on "App signing"

  5. Under "App signing certificate" copy the SHA-1 certificate fingerprint

  6. Go to http://tomeko.net/online_tools/hex_to_base64.php

  7. Paste the SHA-1 in the first field

  8. Copy the text in input field under "Output (base64)"

  9. Presently, open developer.facebook.com/apps

  10. Click on your app

  11. On the left side navigate to "Settings" -> "Basic"

  12. Paste the Base64 text here under key hashes

UPDATE

The steps above must still fully perform.

However, in case you do not want to paste your key on that website, here is an alternative to step 6,7,8 below:

here's a oneliner Node.js command to do the same:

node -e 'console.log(Buffer.from(process.argv[1].split(":").map(hex => parseInt(hex, 16))).toString("base64"))' '5E:8F:16:06:2E:A3:CD:2C:4A:0D:54:78:76:BA:A6:F3:8C:AB:F6:25'

 

15.3k points
edited by

Related questions

0 votes
1 answer 92 views
92 views
Problem : Whenever I try to go to my Logs page the following error shows: “There was an error loading Log Streams. Please try again by refreshing this page.” The problem is that there is another function which is identical except my code which is creating the log files no problem. Any suggestions to resolve my issue?
asked Dec 25, 2019 alecxe 7.5k points
0 votes
1 answer 86 views
86 views
Problem : While doing the drupal 6 to 7 upgrade I am facing a not so helpful message "The website encountered an unexpected error. Please try again later." everytime I go to the certain pages. example) /admin/config What is a best way to find out what is causing ... it? All I can think of right now is to start disabling the contributed modules until that the page works or looking through a logs.
asked Jan 21 jwilliam 3.9k points
0 votes
1 answer 108 views
108 views
Problem : I am having the following error whenever I am trying to open Excel Online in Chrome, But Excel Online in Safari is working fine for me. Does anyone know how to fix this issue? Sign in Something went wrong and we can't sign you in ... . Please try again later. The Microsoft account login server has detected too many repeated authentication attempts. Please wait a moment and try again.
asked Nov 26, 2019 alecxe 7.5k points
0 votes
1 answer 1K views
1K views
Problem : Facing following error sorry, something unexpected happened. try again. (unknown error (empty response) (#1.1357045))
asked Nov 13, 2019 peterlaw 6.9k points
0 votes
1 answer 8 views
8 views
Problem: I am working on Fancybox for the very first time I am trying to display the inline content (it is a div with the image linked to the new page). My div and image are displayed properly in a modal but if a image is clicked to navigate to a new page then in that case I ... website.com/file/id:64/ext:.png" class="img" /></a></div></div> </li> Can someone help me in fixing my fancybox error.
asked Jul 14 Raphael Pacheco 2.3k points