This week, we spotlighted Pinterest's use of the Open Graph, gave some tips on improving app distribution on iOS, and announced that the Mobile Hack Roadshow is coming to Asia.

New App Reporting Flow

We changed the app reporting flow to provide consistent reporting options for people and enable developers to get feedback directly from people. When a user selects either the "Report/Contact this App" link at the bottom of a canvas page or the "Report App" link from the Auth Dialog or Request channel, they will be presented with several granular options on what type of issue they want to report.

The different options will route them to the developer or Facebook depending on the particular issue: If the developer has provided their own User Support URL, located under the "Advanced" tab in the developer app, users will be directed to the developer's help center to report a bug in the app or issues with load time. If the developer does not provide a User Support URL, Facebook will send an email report to the User Support Email address listed.

We noticed that people were reporting issues such as bug reports that should have gone to the developer but instead were being sent to Facebook. This is corrected in the new flow, which applies to all apps.

Graph API errors return an additional code field

We have added an additional field to error responses named code. This field will contain an integer value depending on the type of error. Developers can use this field to discern and group different error responses rather than parsing the text field. We have not altered the content of the text field, so if your apps parse the field to look for error codes, they will continue to work. We will be publishing a list of error codes soon.

Example of the new property:

{
   "error": {
      "message": "An active access token must be used to query information about the current user.",
      "type": "OAuthException",
      "code": 2500
   }
}

Upcoming Breaking Changes on March 1, 2012

  • Removing the third settled callback from Payments. To ensure the best experience for users, we are asking developers to ensure that they are fulfilling the order in the callback with status=placed. We assure you that once we call you with status=placed and you respond with settled, the transaction will be complete and you will be paid. You should not be waiting for the settled callback before fulfilling the order.

    To reduce confusion we are completely removing the settled callback. For more information please read the Facebook Credits Update blog post.

  • Returning up to 960px wide photos in "photo" FQL table and photo Graph API. On 1st March 2012 we will begin returning photos up to 960px wide in the src_big field of the photo FQL table, as well as the source field of the photo object, increasing the current max width of 720px.

Bugs activity between Tuesday, February 14 and Tuesday, February 21

  • 229 bugs were reported
  • 16 bugs were reproducible and accepted (after duplicates removed)
  • 6 bugs were by design
  • 16 bugs were fixed
  • 52 bugs were duplicate, invalid, or need more information

Bugs fixed between Tuesday, February 14 and Tuesday, February 21

Facebook Stack Overflow Activity

Activity on facebook.stackoverflow.com this week:

  • 170 questions asked
  • 123 questions with a score of 0 or greater
  • 50 answered, 41% answered rate
  • 78 replied, 63% reply rate

You may have noticed that with every Operation Developer Love update we include metrics on Facebook related StackOverflow questions. At StackOverflow, the community votes questions up as they deem valid or down if the question seems invalid or irrelevant. In order to only share metrics on questions that the community deems valid, we are updating the metric to only count questions with a score of zero or greater.