Development issue/problem:

I’m getting this error message. When I try to login to the app with Facebook.
It will work correctly the first time you authenticate. After uninstalling my application and trying to connect to Facebook, I get this error.

Another question: After authenticating in the device1 and trying to connect to Facebook on the device2, the same error appears.

The solution I found: if I remove the authentication from the application in the settings of the Facebook application, it works in the above scenario, but it is not the best solution, how can we tell users to do this action?

btnFbLogin.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
if(accessToken != null) {
boolean expires = accessToken.isExpired();
if( !expire) {
performFbLoginOrSignUp(accessToken) ;
}
} else {
LoginButton loginButton = (LoginButton) findViewById(R.id.login_button) ;
callbackManager = CallbackManager.Factory.create() ;

As (loginButton != null) {
loginButton.setReadPermissions(public_profile, email, user_friends) ;

If (CommonUtil.isConnectingToInternet(LoginActivity.this)) {
loginButton.performClick() ;

loginButton.setPressed(true) ;

loginButton.invalidate() ;

loginButton.registerCallback(callbackManager, mCallBack) ;

loginButton.setPressed(false) ;

loginButton.invalidate();
}
}
}
}
}) ;

The example of Facebook is also a problem:
Link to GitHub with Facebook as an example

Stages of reproduction :

How can I solve this problem?

Solution 1:

I’m also facing this problem. Update the hashtag of your key on Facebook.

Solution 2:

The error is due to an invalid hash key.

We can create a hash key with the following command and update it here in Settings-> Basic -> Android HashKeys.

key tool -exportcert -alias ADD_RELEASE_KEY_ALIASE_HERE -keystore ADD_UR_KEYSTORE_PATH_HERE | openssl sha1 -binary | openssl base64

If necessary, you can determine the Relase Key Alias of your keyboard memory with the following command :

Keyboard – list – keyboard ADD_UR_KEYSTORE_PATH_HERE

I also encountered a problem like the HashKey above, the connection works fine if I install the MOT version directly on the device, but if I download the MOT from Play Store and install the application from the store, it shows the same error: the connection fails. The appendix is as follows:

  1. Click here to go to the news management page.
  2. Choose Release Control -> Apply Signature
  3. You can see the SHA1 key in the hexadecimal format of the application form that signs the certificate.
  4. Copy SHA1 in hexadecimal format and convert it to base64 format, you can use this link by using it without SHA1 : Be part of the hexadecimal format.
  5. Go to the Facebook Developer Console and add the key (after conversion to base 64) under Settings -> Base -> Key Hashes.

Solution 3:

ANSWER :

This is a simple attempt to get the message across to those who still have this problem.
The hash I made with the key was somehow wrong. I corrected this:

If you have already downloaded your application from the Game Store and enabled the signing of the Google Play application, there is a solution (at least it worked for me) :

  1. Registration
  2. Click on the request
  3. Now press the left release button.
  4. Press the Signature button in the application
  5. Under Application Signature Certificate, copy the fingerprint of the SHA-1 certificate.
  6. Sync and corrections by n17t01 http://tomeko.net/online_tools/hex_to_base64.php
  7. Insert SHA-1 in the first field.
  8. Copy the text into the input field of the output part (base64).
  9. open developer.facebook.com/apps now
  10. Click on your request
  11. on the left, go to Settings -> Basic.
  12. after the text Base64 here below the key reels
    enter the description of the image here

That should solve the problem.

FIXED

The above steps still need to be fully functional.

However, if you do not wish to enter your key at this stage, there is an alternative to steps 6,7,8 below:

Here is the order of the single link node.js to do the same:

node -e ‘console.log(Buffer.off(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’ ‘5E:8F:16:06:2E:A3:CD:2C:4A:0D:54:78:76:BA:A6:F3:8C:AB:F6:25

Credits: mifi

UPDATE – NOVEMBER 2020

Google has launched a new reading console. From this point you can find the certificate for the signature of the application key here:
fill in the description of the image in here

Solution 4:

It’s about Facebook. Confirmed by the Facebook team.

Give here a description of the image

Decision expected: within 3 days

Solution No 5:

For me, this error was caused by invalid consent sequences. On iOS and Android.

Solution No 6:

Give here a description of the image FnnK.jpg

Solutions —–
Set up LoginBehavior if your phone is equipped with the Facebook application loginButton.setLoginBehavior(LoginBehavior.WEB_ONLY) ;

Solution No 7:

I solved the same problem by replacing the hash of the key,

How to make a keystroke for sharing.
Open the Chrome browser console to convert the Allen key to the base64.

Copy the SHA1 key from the Google game console.

> btoa(‘a1:43:d4:27:c8:04:rr:fr:2g:3b:tg:b5:et:c1:4a:1t:fr:f5:54:5f’.split(‘:’).map(hc => String.fromCharCode(parseInt(hc, 16))).join(‘).

Solution No 8:

This problem occurs because you have already authenticated the application via Facebook, and your code may contain Facebook authentication (find and delete).

Proceed as follows:

  1. Go to Facebook settings.
  2. Uninstall your application.
  3. Make sure you have added the Facebook login to the Facebook developer page and enabled the OAuth client login.
  4. Go to your code and bypass the callback method:

@Override
public void onActivityResult (int requestCode, int resultCode, Intent data) {
super.onActivityResult (requestCode, resultCode, data);
mFacebookCallbackManager.onActivityResult(requestCode, resultCode, data);
as (resultCode == RESULT_OK) {
Intent secondActivityIntent = new Intent(this, RedirectActivity.class);
startActivity(secondActivityIntent);
}
}.

  1. In the Oncreate method, call AccessToken :

accessTokenTracker = new AccessTokenTracker() {
@Check
protected void onCurrentAccessTokenChanged(
AccessToken oldAccessToken,
AccessToken currentAccessToken) {

}
};

accessToken = AccessToken.getCurrentAccessToken() ;

if(accessToken != null && !accessToken.isExpired())
{
GraphRequest request = GraphRequest.newMeRequest(accessToken, new GraphJSONObjectCallback() {
@Override
public void onCompleted(JSONObject object, GraphResponse response) {
if(null!= object) {
try
{
Intention i = new intention (MainActivity.this, Feedback.class);
startActivity(i);
String email = object.getString(email);
String birthday = object.getString(birthday) ;

}
catch (except ex)
{
Toast.makeText(MainActivity.this, ex.toString(), Toast.LENGTH_SHORT).show();
}
{a6}Other.

}
});
packet parameters = new bundle();
parameters.putString(fields,id,name,birthday,link);
request.setParameters(parameters);
request.executeAsync();
}.

Solution No 9:

I had the same problem.

It was a mistake on my part.

key tool -exportcert -alias -keystore | openssl sha1 -binary | openssl base64

When you enter this command, you will be prompted to enter the keyboard password:. I gave keyPassword a storePassword, and it gave no error message, but generated another hash!

Solution No 10:

That’s what I’m referring to,

https://developers.facebook.com/docs/android/getting-started

or simply add the following code to the onCreate() method, which returns the hash of the key.

// Added code to print the hash key
try {
PackageInfo info = getPackageManager(
com.facebook.samples.hellofacebook,
PackageManager.GET_SIGNATURES);
for (Signature: info.signature) {
MessageDigest md = MessageDigest.getInstance(SHA);
md.update(signature.toByteArray());
Log.d(KeyHash:, Base64.encodeToString(md.digest(), Base64.DEFAULT));
}
} catch (NameNotFoundException e) {

capture (NoSuchAlgorithmException e) {

}

Enter the code above to obtain the key you can register.

https://developers.facebook.com/docs/facebook-login/android

Over here. Now it’s gonna work.

It worked for me, and I hope it works for you.

OR

This command may not give you the last hash.

key tool -exportcert -alias YOUR_RELEASE_KEY_ALIAS -keystore YOUR_RELEASE_KEY_PATH | openssl sha1 -binary | openssl base64

To get the last hash or the active android studio hash, look for the hash in Logcat or android studio android monitor while the application is running and run the above error. You’ll get another active keyhash. Once you have placed the desired hash in the console settings, you can login to your application.

Good luck!

login error facebook android,login error facebook,there is an error in logging you into this application fbsdk,login error: there is an error in logging you into this application instagram,oops there was an error logging in with facebook please try again,there is an error in logging you into this application pubg,facebook app dashboard login,facebook messenger unable to login please try again later,there was an error logging you in please try again epic games

You May Also Like

What Technology Do Lawyers Use in 2021?

The technicians are here to stay and there is no middle ground…

How to Delete Blank Pages in Word

Normally, to delete a blank page in a Word document, you must…

How To Get Subtitles On ITV Hub

If you have not heard of ITV Hub yet, it is a…

Download Google Camera 8.1 for TCL 20 Pro 5G [Best GCam]

Google recently released a new version of its Google Camera application that…