Asked  7 Months ago    Answers:  5   Viewed   33 times

Why does it always happen to me?

This happens after my application verify for user user login and redirect user to the authentication page:

But instead of showing the authorization page, Facebook shows an error page with

An error occurred. Please try again later.

Is there any configuration I have to do before try to authenticate my users?

All is done with PHP using the PHP-SDK classes.



I had the same problem after changing the domain of my site. Altough I properly changed the request_uri parameter and updated my app settings with the new domain, the error kept showing up. Then I realized that the ID and the SECRET ID of my Facebook APP had automatically changed with no warning!! The whole thing started working again using the new ID.

Wednesday, March 31, 2021
answered 7 Months ago

You can try this:
1. In your FbApp disable the "require appsecret_proof for server API calls"
2. In your code, after line FacebookSession::setDefaultApplication($app_key,$app_secret);
add this line: FacebookSession::enableAppSecretProof(false);

Saturday, May 29, 2021
answered 5 Months ago

Looks like there is only one nice way to achieve this:

Although /me/groups requires user_groups permission to retrieve groups the user is a member of, it can return groups created by the app without it (given there is a valid access token of course).

So - while it's clearly not as nice and seamless as I wanted it to be - my solution was to create a new Facebook group using the app (requires only a POST request) and move current members to this new one.

Edit: moving members is not a possibility, joining an app group is only possible programatically using the SDK. Therefore, when a user is not a member of this group, I'll prompt them to join. It means that everybody can join and I have to manually ban those I don't like instead of manually allowing those I want to, but given the low publicity, I can deal with this.

Saturday, May 29, 2021
answered 5 Months ago
  1. Make sure you upgrade to the latest NuGet (
  2. Make sure you're doing package restore "The Right Way"

That should resolve the issue.

Tuesday, August 3, 2021
answered 3 Months ago

Apparently there is a bug in PayPal login window. When a password field in the PayPal login contains "&" character, INTERNAL_SERVER_ERROR message is shown (does not matter if credentials are correct or not):

02-09 14:34:01.171: E/RequestError(6618): 500 http response received.  Response not parsable.
02-09 14:34:01.171: E/PayPalService(6618): INTERNAL_SERVER_ERROR
02-09 14:34:01.341: E/LoginActivity(6618): login error: INTERNAL_SERVER_ERROR

If there is no "&" character in password and credentials are not correct, a valid error message is shown in the log:

02-09 14:33:48.741: E/RequestError(6618): , Mobile Login failed.
02-09 14:33:48.746: E/PayPalService(6618): 10803
02-09 14:33:49.206: E/LoginActivity(6618): login error: 10803

My password contained "&" character. When I changed my password not to contain it, I was able to login.

Follow full story on PayPal Android SDK GitHub page.

Monday, August 30, 2021
Ramy Al Zuhouri
answered 2 Months ago
Only authorized users can answer the question. Please sign in first, or register a free account.
Not the answer you're looking for? Browse other questions tagged :