Platform Updates: Operation Developer Love

By Eugene Zarakhovsky - Wednesday, December 28, 2011 at 1:00pm

Last week we announced Mobile Hacks in New York and Boston and outlined new features we are making available to games developers.

Open Graph Approvals

With the worldwide rollout of Facebook Timeline underway, we are beginning to the process of reviewing Open Graph actions submitted for approval. We expect to start approving actions in January and will post an update once we begin to approve actions in earnest. Once the action is approved, the person who submitted the action for approval will receive a Facebook notification and the app can begin publishing this action to all users.

Mobile Hacks

This week we announced our Mobile Hacks in New York (January 18th) and Boston (January 20th). More information and signup instructions are available in the blog post linked. This is similar in format to the Mobile Hack we ran in Palo Alto in October and is highly recommended for mobile developers.

90-day Breaking Change Announcement

Effective April 1st, 2012 the URLs provided for the redirect_uri parameter and any action links in Feed Dialog posts must be owned by the app. This means that the URLs must match your app's Canvas URL or the 'App Domains' specified in your app settings. This has been added to the Platform Roadmap.

Platform Policies translated

We have translated the Facebook Platform Policies into thirteen additional languages as an aid to our developers. We will also translate the documents into additional languages based on demand.

العربية	中文(简体)	中文(台灣)	Deutsch	Español	Français	עברית
Italiano	日本語	한국어	Polski	Português	Türkçe

Upcoming changes on January 1, 2012

Deprecating the FB.Data.* JS SDK APIs. This will be no longer supported and will not be available to new apps.

Deprecating FB.Canvas.setAutoResize. We have renamed FB.Canvas.setAutoResize to FB.Canvas.setAutoGrow so that the method more accurately represents its function. Fb.Canvas.setAutoResize will be removed.

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" 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 correct request_id format and deleting requests appropriately. Details in this blog post

Enforcing Credits Policy We have added a new policy to the Facebook Credits Terms that prohibits routing Credits from one app to another app without our prior authorization.

2.14 You may not accept Credits in one app and deliver or 
transfer the purchase to the user in another app without 
our prior authorization. For example, an app solely designed
to facilitate transactions is not permitted.

Apps that are not compliant by January 1, 2012 run the risk of having their Credits disabled shortly after.

Please refer to the Platform Roadmap for more information on these and other upcoming changes.