Facebook Graph API Not Functioning after Migration from v2.2 to v2.3

Upon upgrading to v2.3 of Facebook's Graph API, developers have encountered issues with certain API requests failing to return data. This article explores the specific problems encountered and provides solutions based on changes introduced in the latest version of the SDK.

Problem Description

Developers have reported that API requests that previously worked in v2.2 are now returning no results in v2.3. Specifically, the following requests have been affected:

• /me/albums with fields=albums
• /me without any fields specified (used to retrieve the user's birthday)

Solution

The issue stems from changes made in v2.3 to the format of JSON responses returned by the OAuth access token endpoint. In SDK version 3.2.2, the getAccessTokenFromCode() function incorrectly parses the JSON response as an array instead of an object, resulting in the retrieval of an incorrect user access token.

To resolve this issue, the getAccessTokenFromCode() function should be updated to parse the JSON response correctly:

$response = json_decode($access_token_response);
if (!isset($response->access_token)) {
  return false;
}
return $response->access_token;

Additional Updates for Extended Access Tokens

For apps using extended access tokens, a similar change is required in the setExtendedAccessToken() function:

//Version 2.3 and up.
$response = json_decode($access_token_response);
if (!isset($response->access_token)) {
  return false;
}

$this->destroySession();

$this->setPersistentData(
  'access_token', $response->access_token
);

Conclusion

By addressing the aforementioned changes in JSON response parsing, developers can ensure that their API requests function as expected in Facebook's Graph API v2.3.