Django-facebook
Django-facebook copied to clipboard
tschellenbach
Time to upgrade :)
https://developers.facebook.com/docs/apps/upgrading/?utm_source=notice&utm_medium=email&utm_content=B&utm_campaign=api
Just ran into this the other day. Actually, people who have created their Facebook apps after API V2 was released already need the upgrade, and December 25th isn't the cutoff.
From developers.facebook.com/docs/apps/versions:
Can my app make calls to versions older than the current version?
An app can make calls to the version of the API that was the latest available when the app was created, as well as any newer, un-deprecated versions launched after the app is created.
Here's an example:
If your app was created before the launch of v2.0, while v1.0 was available, then it will be able to make calls to v1.0 until the expiration date of that version. If your app was created after v2.0 was released, it will be able to make calls to v2.0 until the expiration date of that version, and any subsequent versions (v2.1 etc) until their expiration dates.
In my app (which I created this week) I'm seeing that I always get v2.0 responses, even if I explicitly ask for the versioned v1.0 API. Anyone else run into this?
I was looking at patching the request method of the open_facebook API for V2, since that's what I needed, not sure though in what other areas changes are needed. Maybe you're already looking at it? Or if you tell me what other areas need changing, I could probably do a pull request too.
Edit: Or well, actually, specifically I was looking at patching the 'me/permissions' parsing
@sfrdmn I hope this response isn't too late, but if you created your app "this week" (AKA July 11th, 2014 based on your post time), any calls to the Facebook SDK using access tokens generated by your app can't access v1.0 of the SDK, only v2.0 and beyond.
Any attempts to access v1.0 (e.g. making a request to graph.facebook.com/v1.0/me) is automatically changed to v2.0 by Facebook internally. From Facebook:
For apps created on or after April 30th 2014, making API calls without specifying a version number is equivalent to calling v2.0 of the API. These apps won't be able to call v1.0 of the API.
I suppose this is Facebook's subtle way of preventing new apps from using old versions of their SDK.
The issue now is letting users specify a version of the SDK they want to access, so that v1.0 apps can specify using v2.0 of the SDK rather than using the default v1.0 of the SDK. As I noted above, this is useful only to apps looking to upgrade since apps cannot downgrade (e.g. create an app today and trying to use v1.0).
Looks like I'll have time in September to give this library some much needed polish.
Please keep on submitting issues you run into!
Prevent Broken Experiences in Your Mobile Apps - We Recommend Upgrading to v2.0+ Before December 25th
Is this on the roadmap by chance? It's the top comment in the link that was referenced at the beginning of this thread:
- https://developers.facebook.com/docs/apps/upgrading/
Im going to make time for it sooner or later. If anybody else is picking it up be sure to post an issue about it so we dont do double work. On Oct 25, 2014 7:47 PM, "Troy Grosfield" [email protected] wrote:
Prevent Broken Experiences in Your Mobile Apps - We Recommend Upgrading to v2.0+ Before December 25th
Is this on the roadmap by chance? It's the top comment in the link that was referenced at the beginning of this thread.
— Reply to this email directly or view it on GitHub https://github.com/tschellenbach/Django-facebook/issues/465#issuecomment-60490753 .