These previously-announced changes have been completed. For a list of upcoming changes, check out the Roadmap. For a more detailed list of non-breaking changes that have gone out, check out the Change Log.
June 6, 2012
Removal of FBML
FBML apps will no longer work on Platform. The "FBML Removal" migration will appear and will be enabled for all apps. It will be possible to disable the migration, thereby re-enabling FBML, until July 5, 2012 when the migration and all FBML endpoints will be removed completely.
XMPP Connections must be done over TLS
Apps connecting to Facebook's XMPP service will be required to use STARTTLS for all connections. We will start rejecting unencrypted connections.
May 2, 2012
offline_access Permission Removal
Theoffline_accesspermission is deprecated and will be removed July 5, 2012. Until then, you can turn this change on or off using the "Remove offline_access permission" migration. On May 2, 2012, we will automatically turn the migration to "enabled" for all apps. If this breaks your app, you can turn the migration back to "disabled" until July 5, 2012 when it will be permanently "enabled" for all apps. Please see the Removal of offline_access Permission doc for more details.
Removal of group_type and group_subtype columns from group FQL table
We will remove thegroup_typeandgroup_subtypecolumns of thegroupFQL table. Please ensure that your apps are not utilizing these columns.
Removing support to claim Domains using Page ID - Originally scheduled for April 1st, 2012
We will remove the ability to claim domains with a Page ID. The recommended option for claiming domains is with an App ID or User ID and existing domains that have been claimed will continue to work fine. After claiming domains, owners are able to view insights or run Domain Sponsored Stories. See the Insights documentation for more on the updated domain claiming flow.
April 4, 2012
Making deprecated SDK repositories private
We will make the Python and C# SDK repositories on GitHub private. These repositories are deprecated and may not work as expected due to changes in our auth system.
Removing canvas_name field from application object - Originally scheduled for February 1st, 2012
We will be removing thecanvas_namefield in favor ofnamespacefield on the application object.
February 15, 2012
Pages Insights Metrics Deprecations
We are in the process of deprecating some old Page Insights. We announced this in a number of forums, but failed to outline this change in our Platform Roadmap per our breaking change policy. Our apologies. You can find a full list of the Insights to be deprecated from the Insights documentation. These Insights will be completely removed from API on Feb 15th 2012. Please make all necessary updates as soon as possible so that you can transition smoothly.
February 1, 2012
Removing App Profile Pages
We will be deleting all App Profile Pages and redirecting all traffic directly to the App. For more information, please refer to the blog post.
Removing REST Support for Ads API
We will be removing REST support for the Ads API. All Ads API developers now use the Graph API.
January 1, 2012
Removing the FB.Data.* JS SDK APIs
These will be no longer available.
Deprecating FBML
FBML will no longer be supported as of January 1, 2012. Aside from security and privacy related bugs, we will not fix any bugs related to FBML after January 1, 2012. On June 1, 2012 FBML endpoints will be removed from Platform.
All apps will be opted into "Upgrade to Requests 2.0" and "Requests 2.0 Efficient" Migrations
Existing apps will be opted into “Requests 2.0 Efficient” and "Upgrade to Requests 2.0" migrations and all developers must ensure that they are using the correctrequest_idformat and deleting requests appropriately. Details here.
Enforcing Credits Policy
We have added a new policy to the Facebook Credits Terms that prohibits routing Credits from one application to another application without our prior authorization.
2.14 You may not accept Credits in one application and deliver or transfer the purchase to the user in another application without our prior authorization. For example, an application solely designed to facilitate transactions is not permitted.Applications that are not compliant by January 1, 2012 run the risk of having their Credits disabled shortly after.
December 1, 2011
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 deprecatingcode_and_tokenand need developers to usecode%20token. Everything is identical, just replace_and_with encoded <space> (%20).
Deprecating Dashboard APIs
These APIs (that start with "dashboard.") are no longer supported and will not be available past this date. This does not include the Dashboard count APIs which will deprecate on the FBML and Request 1.0 schedule (no support past Jan 1st 2012, and removed June 1st 2012.
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.
November 1, 2011
manage_notifications Permissions Migration
To read or manipulate a user’s notifications, we will require you to get themanage_notificationspermission.
October 1, 2011
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.
Apps on Facebook Authentication and Security Migration (HTTPS)
All Canvas and Page tab apps must convert to processsigned_request(fb_sigwill be removed) and obtain an SSL certificate for use in "Secure Canvas URL" and "Secure Page Tab URL" (unless you are in Sandbox mode). You must provide an SSL certificate in the Dev App settings to avoid having your app disabled.
auth.promotesession Deprecation
This method is deprecated and will be removed.
manage_pages Permission Required to Access User Accounts (/me/accounts)
We are modifying access to the FQLpage_admintable and thegraph.facebook.com/me/accountsendpoint. 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 themanage_pagespermission in order to obtain access to this information.
June 11, 2011
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.
June 3, 2011
Requiring Access Token for Feed Connection
We will require an access token toGETfromPROFILE_ID/feed.
April 18, 2011
Removing "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.
March 11, 2011
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.
No comments:
Post a Comment