Bring into explicit v2.5 graph api compliance

Bug #1632700 reported by Alberto Mardegan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Facebook Scope
Confirmed
Medium
Unassigned

Bug Description

Two graph API calls are not explicitly using graph api v2.5.

They should be.

== Old Description

From Facebook:

"Ubuntu currently has access to Graph API v2.1 which will reach the end of its 2-year lifetime on 30 October, 2016. To ensure a smooth transition, please migrate all calls to Graph API v2.2 or higher."

Here's a list of endpoints we are using and which need to be updated:

GET {album-id}
GET {user-id}
GET {user-id}/notifications
GET {user-id}/feed
GET {user-id}/home

Tags: backlog
Revision history for this message
Kyle Nitzsche (knitzsche) wrote :

facebook-scope (which is really the facebook photos scope) uses graph api version 2.5 which is available until 12 April 2018:
https://developers.facebook.com/docs/apps/changelog

Revision history for this message
Kyle Nitzsche (knitzsche) wrote :

All graph API calls are explicitly v2.5 except for two, which are silent on graph api version. Both of these calls work as is after the 2.1 api shut down:

https://graph.facebook.com/me
* used to get albums

This works fine when the api version is specified to 2.5:
https://graph.facebook.com/v2.5/me

The code should be modified to set v2.5 explicity.

https://graph.facebook.com/ALBUM_ID
This works when the API is set to 2.2 but NOT when it is set to 2.5.

The code should be modified to bring this call into conformance with v2.5 and to set v2.5 explicitly.

summary: - Facebook is deprecating the 2.1 API
+ Bring into explicit v2.5 graph api compliance
description: updated
Changed in facebook-scope:
status: New → Confirmed
importance: Undecided → Medium
tags: added: backlog
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.