For 2011, there are a few big changes on the Facebook development platform (such as the OAuth 2.0 and new version of SDKs). Though we cannot tell exactly what will happen in 2012, there are already a few breaking changes that Facebook has alerted us about for 1Jan2012.
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 here
- Enforcing Credits Policy We have added a new policy to the Facebook Credits Termsthat 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.
So, before you take your X’mas leave, make sure you have planned and acted for the above items.
Among them, the setAutoResize should be the easiest one to handle. Simply do a global search-n-replace in your code and that’s all. The next one that I think you should check is about the “Requests 2.0 Efficient”.