This week, we encouraged all apps to upgrade to Requests 2.0 so that as a developer, you only need to worry about one way of updating users about outstanding items in your app - send requests.

Determine all apps owning a test user

We previously announced that test accounts can be shared between apps. We’ve now added the ability to retrieve all apps owning a test user:

GET "TEST_USER_ID"/ownerapps

It needs to be called with access token of one of the owner apps. Here’s a PHP example on creating the test user and retrieving all apps owning a test user:

<?php

  //owner_app_id will create the test user
  $owner_app_id = 'OWNER_APP_ID';
  $owner_app_secret = 'OWNER_APP_SECRET';

  $owner_token_url = "https://graph.facebook.com/oauth/access_token?" .
    "client_id=" . $owner_app_id .
    "&client_secret=" . $owner_app_secret .
    "&grant_type=client_credentials";

  $owner_access_token = file_get_contents($owner_token_url);

  //create test user
  $request_url ="https://graph.facebook.com/" .
    $owner_app_id .
    "/accounts/test-users?installed=true&permissions=read_stream&" .
    $owner_access_token . "&method=post";

  $result = file_get_contents($request_url);
  $obj = json_decode($result);
  $test_user_id = $obj->{'id'};

  //retrieve all apps owning a test user
  $request_url ="https://graph.facebook.com/" .
    $test_user_id . "/ownerapps&" .
    $owner_access_token;

  $result = file_get_contents($request_url);
  echo("owner apps= " . $result);

?>

Timestamp update on Dev Site pages

We’ve added timestamps at the bottom left of pages on the Dev Site so that you’ll know when pages were last updated.

Limit on number of properties displayed for stream stories published via API

We’ve put a limit to the number of key/value pairs that will be displayed on stream story properties published via the API. You can continue to publish an unlimited amount of key/value pairs, but we will only display the first 3 key/value pairs on the News Feed.

Submitting great bug reports

We have ramped up the number of people triaging bugs and have been able to touch a progressively larger number of bugs each week. When we have repro info from the start, it makes it so much easier for us to reproduce the bug ourselves and to get the bug into the pipeline to get fixed. We aggressively mark all bugs without proper reproduction steps as “needs repro”.

To ensure we can immediately understand and get to work on fixing the bug you’re reporting, here are some helpful tips:

  • Check if your bug has already been filed, so you can simply subscribe and comment with any relevant repro steps for your case.
  • Provide step-by-step instructions including URLs and/or code snippets that any Facebook developer could easily follow to reproduce the bug. Include any and all user IDs, Page IDs, app IDs, etc. that you use as well as an explanation of how you got any of the access tokens you’re using.
  • Include a screencast video or trace logs.

If you’re looking for a good example, check this out. Please add a comment below if you have any thoughts or suggestions on what we can be doing better.

Fixing Bugs
Bugzilla activity for the past 7 days:

  • 129 new bugs were reported
  • 63 bugs were reproducible and accepted (after duplicates removed)
  • 15 bugs were fixed (13 previously reported bugs and 2 new bugs)
  • As of today, there are 4,141 open bugs in Bugzilla

Forum Activity
Developer Forum activity for the past 7 days:

  • 363 New Topics Created
  • 220 New Topics received a reply
  • Of those 220, 66 were replied to by a Facebook employee
  • Of those 220, 135 were replied to by a community moderator

Ben, a Platform Engineer, is hoping timestamps on the Dev Site are helpful. Transparency FTW!