SERVER_ERROR: [code] 1675030 [message]: Error performing query –

Development issue/problem:

I use a Facebook connection on Android.
Code:

callbackManager = CallbackManager.Factory.create();
loginButton loginButton = (LoginButton) this.findViewById(R.id.login_button);
loginButton.setReadPermissions(email, public_profile);
loginButton.registerCallback(callbackManager, new FacebookCallback() {
@Override
public void onSuccess(LoginResult loginResult)) {
// request code
Log.println(Log.ASSERT, FB, inicio session);
}

@Override
public void onCancel() {
Log.println(Log.ASSERT, FB, OP NO completada);
// Request code
}

@Override
publicly void onError(FacebookException exception) {
Log.println(Log.ASSERT, FB, Errro de sesion);
exception.printStackTrace();
// Application code
}
})

but still gets the next mistake:

I added a folding resolution.

How can I solve this problem?

Solution 1:

I found the solution, it happens when you don’t have a user note in your application.

Enter application
Select a role in the control panel

And add test users. If you try to log in with test users, the application works flawlessly.

Solution 2:

The documentation on Facebook is poor. I had to add the three default permissions to make this work.

loginButton.setReadPermissions(email, public_profile, user_friends) ;

Solution 3:

@Danew is the correct answer, but I want to add something. These errors only occur when your application is under development. Follow this link and select your request. Then there are two things you can do here. On the Roles tab, you can only allow your friends to log in, or you can select App Review and make your application public, after which everyone can log in.

Solution 4:

I had a similar problem because the Firebase user interface specified android:-value. Here’s how I solved this problem:

…

Solution No 5:

All the answers above didn’t help me because you used this command.

key tool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keyystore | openssl sha1 -binary | openssl base64

to get the key reels you put in the Facebook configuration.

It requires a password, I didn’t set one at first, so the problem occurred when I logged in with the android password. It worked!

Solution No 6:

Exit protocol : SERVER_ERROR : Code] 1675030 [Message] : Error in the execution of the request

And the exact solution for this specific problem (error searching)

Answers @aloha – this is an update of the access request.

loginButton.setReadPermissions(email, public_profile, user_friends) ;

1. Find out where the Facebook login button was used.
2. Then set the ReadPermission button to e-mail, public_profile, user_friends.

Image reference

Exit protocol : The application is not configured. This application is still in development mode. and you do not have access to it. register a test user or ask the application administrator for authorization.

1. The question is not in real time
2. You are not registered as an administrator or tester at
   https://developers.facebook.com/app/yourapp.
3. If the Facebook application cannot be used in live mode, you will need a hash key to test it. because the application is not yet in live mode. Facebook does not provide access.

HOW TO CHANGE THE LIVE PAGE MODE
1. Go to: https://developers.facebook.com
2. 2. Select an application from the My Apps3 list. Select an application from the My Apps list. Switch the switch from the OFF to the ON position.

1. go to: https://developers.facebook.com2. select the request from the My Requests list3. go to : Roles > Roles > Click on Add, for example B. Admin
4. Search for your new Facebook administrator/tester account.

5. the administrator must enter the Facebook password to confirm. then send
.

the new administrator should go to the developer.facebook page and accept
6. go to: https://developers.facebook.com

7. Profile > Requests > Confirm


8. Congratulations on your appointment as the new director.

DEVELOPMENT INSTALLATION See the
registration documentation on Facebook at https://developers.facebook.com/docs/android/getting-started/#create_hash.

I prefer the code (examples of applications that solve problems).

it produces a hash key. You can update it to

https://developers.facebook.com/apps/yourFacebookappID/settings/basic/
on Android > Key heels

a step-by-step guide on how to get the HashKey.

1. First add the code to a method you created.

1. Launch the application and search for KeyHash in Logcat.

The step-by-step update process at Facebook Developer.

1. Open the developer’s Facebook page. You must have access to the developer’s Facebook page to update it: https://developers.facebook.com.
2. Proceed to the next step.

Solution No 7:

Actual development mode
Check the status of the development mode. He must still be alive.
First you need to add the privacy URL of your own Facebook project that you use to set up the Facebook connection or… ….. Then activate the developer mode (Enable).

Solution No 8:

In my case, the generated hash key was wrong because I used the wrong OpenSSL.
I used openssl-0.9.8k_X64.zip instead of openssl-0.9.8e_X64.zip and it generated the wrong hash key that caused this problem, hopefully it helps someone, I wasted about 8 hours trying to fix it.

Solution No 9:

In my case the problem was a badly generated keyash sent to the solution of the Facebook
application page found in this article https://developers.facebook.com/docs/facebook-login/android/advanced.

Manually check the Key Hash – You can print the Key Hash sent to Facebook and use this value in the App Dashboard. Make this change to onCreate() as part of your core business:

Try
{
PackageInfo info = getPackageManager().getPackageInfo(
com.facebook.samples.loginhowto,
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) {

}

Solution No 10:

This error also occurs in other situations – even if your application is public or if you are registered as a tester.

Check that you resolves to the correct Facebook application id, especially if you specify it dynamically with the gradle build instead of hard-coding in string.xml.

Related Tags:

facebook developer,e/fb4a.graphservicequeryexecutor: query error,error performing query — oculus store,app not setup this app is still in development,server_error: [code] 1675030 [message]: error performing query. [extra]: react native,graphql server responded with error 1675030: error performing query. facebook,fbapierrordomain 1675030,login error facebook android,kotlin facebook login,there’s an issue with its implementation of facebook login android,android login with facebook and google example,error performing query in hindi