Developer news
Platform Updates: Operation Developer Love

Last week we introduced the Subscribe Button for Websites, announced the removal of App Profile Pages on February 1st, 2012, provided a recap on our recent Social Games Hack and published a tutorial on debugging Open Graph apps.

Finally, we updated the JavaScript SDK to only support OAuth 2.0. This new JavaScript SDK was first announced in July with the requirement that all apps to migrate by October 1, 2011. If your app was affected, read more about the specific changes that you need to make here. A friendly reminder that it is important to follow the Facebook Developer Blog or the Roadmap for breaking change updates. This can be done by email or RSS.

Platform Changes

This week we completed the discontinuation of the Dashboard APIs with the exception of dashboard.incrementCount, dashboard.decrementCount, dashboard.setCount and dashboard.getCount methods. All apps should upgrade to the new Requests 2.0.

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 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 info on these and other upcoming changes.

Bug Activity from 12/6 to 12/13

  • 210 bugs were reported
  • 89 bugs were reproducible and accepted (after duplicates removed)
  • 61 bugs were by design
  • 27 bugs were fixed
  • 71 bugs were duplicate, invalid, or need more information

Bugs fixed from 12/6 to 12/13

Activity on this week:

  • 140 questions asked
  • 16 answered, 11% answered rate
  • 50 replied, 36% reply rate