Developer Roadmap – Facebook Developers

Developer Roadmap


In the spirit of openness and transparency, we publish this roadmap to help developers plan for changes that may require code modifications. Like all roadmaps, it may shift slightly, but we will share insight into what is happening as details become available.

We encourage developers to subscribe to our blog, where we announce rollout plans and timing. If you have questions about these changes, please share them in the Developer Forum.

Upcoming changes

Date Item
October 1, 2011

1. OAuth 2.0 Migration

As we announced in May, all apps must migrate to OAuth 2.0 for authentication and expect an encrypted access token. The old SDKs, including the old JS SDK and old iOS SDK will no longer work.

2. Apps on Facebook Authentication and security migration

All Canvas and Page tab apps (that are not using FBML) must convert to process signed_request (fb_sig will be removed) and obtain an SSL certificate for use in ‘Secure Canvas URL’ and ‘Secure Page tab URL’ (unless you are in Sandbox mode).

3. Auth.promotesession deprecation

This method is deprecated and will be removed.

4. manage_pages permission required to access user accounts (/me/accounts)

We are modifying access to the FQL page_admin table and the endpoint. Previously, with basic permissions granted, an app could go to this endpoint or the FQL table to access the list of a user\’s apps and Pages. We are going to require that apps have the manage_pages permission in order to obtain access to this information.

November 1, 2011

1. manage_notifications Permissions migration

To read or manipulate a user’s notifications, we will require you to get the manage_notifications permission.

December 1, 2011

1. OAuth spec migration

In order to be compliant with the OAuth spec we have made changes to our auth APIs. As part of this update, we will be deprecating ‘code_and_token‘ and need developers to use ‘code%20token‘. Everything is identical, just replace ‘_and_‘ with encoded <space> ‘%20‘.

2. Deprecating Dashboard APIs

These APIs are no longer supported and will not be available past this date.

3. Apps on Facebook: FB.Canvas.getPageInfo must be called with callback

The FB.Canvas.getPageInfo method will have to be called with a callback function. This was previously not required. See this blog post for more information.

Januray 1, 2012

1. Deprecating the FB.Data.* JS SDK APIs

This will be no longer supported and will not be available to new apps.

Q2 2012

1. Deprecating <fb:board>

This will be no longer supported and will not be available to new apps.

Completed Changes

Date Item

Canvas Apps and Page Tabs: No new FBML apps

We will stop allowing new FBML apps, but will continue to support existing FBML tabs and apps. Instead, we recommend using iframes.

Complete (6/3/11)

Graph API: Requiring access_token for PROFILE_ID/feed/

We will require an access token to GET from PROFILE_ID/feed.

Complete (6/11/11) Tools: New Developer app

We are building a new version of the Developer app for managing your application’s settings and will be adding features such as the ability to easily create and manage test users, manage large numbers of apps, manage users with special privileges (admin, developer, tester, insights), and more.


Deprecations: “year” and “status” properties of “affiliations” column in “user” FQL table

These properties will be removed from the “affiliations” column. You should use the “education” property of the User object in the Graph API or the “education_history” column of the user FQL table instead.


Migrations: Comments v1 migration

As a follow up to a note sent to all developers using Comments Box v1, we will upgrade all sites to the new version of the Comments Box to ensure that Facebook users have access to the latest version across the web. Upon upgrade, ordering of the comments will shift from chronological to showing the most socially-relevant comments first. Also, please note that the upgraded version of Comments no longer supports custom CSS. You can upgrade today by adding the ‘migrated=1’ parameter to your existing <fb:comments> tag. Please note that once upgraded, you cannot switch back.


Migration: New JavaScript SDK (PHP SDK v.3.0 available May 20)

Updates to the PHP and JS SDKs available that use OAuth 2.0 and have new cookie format (without access token).


Migration: Minor PHP SDK update to accept new JavaScript SDK cookie format

Updates to the PHP SDK to use new JS SDK cookie format.

Updated on Monday

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s