Since last Wednesday’s update, we announced App Center global rollout, and launched Facebook SDK 3.0 Beta for iOS. We published details on the Photo Hack Day in San Francisco.

Javascript SDK cleanup

We are continuing to reduce the number of methods exposed by the global FB object in the Javascript SDK and are now logging a warning to the console whenever a non-documented method is used. At a later time, these will all be stubbed with empty functions before finally being removed entirely from the FB object. For the list of publicly available methods, please see the Javascript SDK documentation.

October migration now available

The “October 2012 Breaking Changes” migration is now available for you to test your apps to see if they will be affected by the breaking changes happening on October 3rd, 2012. Check out the Developer Roadmap for more information on what changes are included in the migration.

Weekly Stats

The following stats are for activity between Wednesday, July 4 and Wednesday, July 11.

Bugs activity between Wednesday, July 4 and Wednesday, July 11

• 174 bugs were reported
• 44 bugs were reproducible and accepted (after duplicates removed)
• 14 bugs were by design
• 54 bugs were fixed
• 78 bugs were duplicate, invalid, or need more information

Bugs fixed between Wednesday, July 4 and Wednesday, July 11

• Unable to add App Privacy Policy URL
• FB JS SDK does not refresh cookies & access tokens anymore
• Facebook Authentication Error code 100: “This authorization code has been used.”
• the FB.Canvas.setAutoGrow() something not working
• App Center Submit
• FB registration plugin validation stopped working
• Adding attachment causes bug creation to fail to create with a POST 500 server error
• No longer able to get OAuth token via Facebook in my Windows Phone 7 application
• Sandbox apps redirecting me to 4oh4.php
• Login button gives “You have already authorized” response
• Mobile Comments Plugin – Stuck in infinite loop
• display=touch forwards to “Page you requested was not found”
• login-button with registration-url not invoking onlogin callback + does not display as ‘Register’ if user has not authorized the app
• Bugs losing comments and subscribers
• Facebook request displays FB Login Button
• HeroMessagingServerException – No more data to read.
• App center submission error: missing other language information
• Edit app lead to page not found
• Graph API returns user picture as an object when not logged in to Facebook.
• FB.login does not trigger callback + does not close itself on localhost:8080
• A document page is completely broken and can’t even click “Report Documentation Bug”
• Cannot enable Enhanced Auth Dialog
• Mobile comments are no longer fluid
• Page Administration not created for webpages when admin clicks ‘Like’
• Dislpay name cant be changed on AppCenter- Save doesnt “hold water”
• Basic Settings on Edit App Page Empty
• Official Facebook WordPress plugin fails to publish actions for Auth Dialog Preview User
• Sandbox canvas page requires secure URL
• Unreachable URL warning near comments in bug tool
• Can’t save advanced settings (There was a problem saving your changes. Please try again later.)
• Request ID’s not passed when User enters Canvas via Facebook Notification
• iOS Client Library throws exception while extending access token
• Error in enable access offline
• Open Graph action links in Timeline rendered by the FB Mobile apps are broken with App Center release
• Locale param for iframe Like button causes incorrect like count
• Facebook raise error, when trying to edit extended preferences of application
• send dialog changes a https link into http
• API Error Code: 11 – FB.login failing to work on Blackberry device
• app request url doesnt contain app request_id parameter when namespace is not defined
• Image quality is very very poor after upload
• Javascript SDK URI Error in Android WebView and iPhone UIWebView
• Malformed FQL query made via api results in all.js error
• App Request page is broken when ?scrollto= is in URL.
• iPhone App/iPhone Safari/Android Mobile Browser: Timeline links not redirecting to correct URL
• FB.ui – loading forever if user is logged in / works fine if user needs to login
• FB.api doesn’t work at Opera browser when using https connection
• Post-Authorize Redirect URL issue
• all.js does not check origin in FB.provide.PostMessage.onMessage
• Built-In actions can’t be resubmitted
• Canvas height is not working
• Facebook API not work in Opera
• Text direction problem on credit dialog
• XDomain issues in opera
• video upload doesn’t work in Hackbook example

Activity on facebook.stackoverflow.com between Wednesday, July 4 and Wednesday, July 11

• 431 questions asked
• 332 questions with a score of 0 or greater
• 109 answered, 33% answered rate
• 200 replied, 60% reply rate

Since last Wednesday’s update, we launched an API that allows you to get the user’s preferred currency along with the conversion rate to Credits.

Streamline review of your Open Graph actions and objects

This week we published a new guide titled Creating Usage Instructions. When you submit your Open Graph actions and objects for review, you must include usage instructions. This guide outlines how to create clear instructions so that we can quickly review your submissions.

Javascript SDK cleanup

We are continuing to reduce the number of methods exposed by the global FB object in the Javascript SDK and are now logging a warning to the console whenever a non-documented method is used. At a later time, these will all be stubbed with empty functions before finally being removed entirely from the FB object. For the list of publicly available methods, please see the Javascript SDK documentation.

Breaking changes effective today

As announced in April per our 90-day breaking change policy, ten breaking changes are going into effect today:

1. Event GETs from Graph API/FQL will require an access token
2. Removing display=wap dialogs
3. Removing some event FQL object fields
4. Coordinate-less tags
5. Removing bookmark.add and profile.addtab dialogs
6. Moving “type” property into “metadata” array
7. Removal of FBML
8. Updating Page “hours” property
9. Batch API exception format
10. Removing timezone from event times

For the full details on all these changes, please check out the Developer Roadmap.

October 2012 breaking changes (90-day notice)

The following changes will go into effect on October 3rd, 2012:

Built-in like/follow action required
We will stop allowing the use of Custom Open Graph “like” and “follow” actions now that there are built-in “like” and built-in “follow” actions. Please convert any custom “like” or “follow” actions you may have created to instead use the built-in “like” or “follow” actions.

Removing Bookmark URL – Originally scheduled for December 1, 2011
As mentioned on the blog, this optional field was originally created to help developers track user referrals from app bookmarks. We now pass a ref parameter to let you know that the user is coming from a bookmark (i.e. ref=bookmarks). As such, we will remove the “Bookmark URL” field from the apps settings.

The following change can be enabled/disabled using the “Remove offline_access” migration until October 3rd when it will go into effect permanently for everyone:

offline_access permission removal

The offline_access permission is deprecated and will be removed October 3rd, 2012 (originally scheduled for July 5th). Please see the Removal of offline_access Permission doc for more details.

The following changes can all be enabled/disabled using the “October 2012 Breaking Changes” migration (will be available for use by July 18th) until October 3rd when they will go into effect permanently for everyone:

Removing Live Stream plugin
The Live Stream plugin has been deprecated and will render the Comments Box plugin in its place. While it offers similar functionality, there are a few functional differences. Please see the Live Stream plugin documentation for more info.

Summary field being replaced by description field
Because the two fields were somewhat redundant, we will be removing the “Summary” field (found in the “Auth Dialog” section of an app’s settings) and instead using the “Description” field (found in the “Advanced” section of an app’s settings) in places where “Summary” was previously used.

Removing position field for photos
The position field in both the photo FQL table as well as the Photo Graph API object will start returning 0 for all photos. The photos connection on an Album object in the Graph API will continue to return photos in the order they appear in the album. FQL queries on the photo table that have a WHERE clause containing the aid or album_object_id columns will return in the correct order as well without needing an ORDER BY position clause.

/picture connection will return a dictionary when a callback is specified
We will start returning a dictionary containing the fields url, height, width, and is_silhouette when accessing the /picture connection for an object and specifying a callback property. Currently we just return the picture URL as a string.

Weekly Stats

The following stats are for activity between Wednesday, June 27th and Wednesday, July 4th.

Bugs activity

• 217 bugs were reported
• 34 bugs were reproducible and accepted (after duplicates removed)
• 8 bugs were by design
• 17 bugs were fixed
• 66 bugs were duplicate, invalid, or need more information

Bugs fixed

• Mobile Web feed links have “apps/[NAMESPACE]” twice
• setAutoGrow() not working.
• JavaScript SDK (all.js) error in FireFox: n.onload is not a function
• Deleted app still exist
• FB.getLoginStatus errors for logged out users when the app has an alcohol restriction
• Open Graph Insights not updating when you filter by action
• Cannot view “Roles” for a particular app
• Status: Changes needed
• No Facebook Insights data since June the 12th
• Already authorized
• photo URLs now contain underscores which causes issues in Java
• Mobile comments to wide when no width is set.
• data-width takes no effect on facepile
• phpunit failure on PHPSDKTestCase::testAppSecretCall
• Information concerning automatic creation of App Profile Pages outdated.
• FB.Canvas.setUrlHandler() doesn’t call callback function
• Facebook PHP SDK Deficiency in handling cluster environment

Activity on facebook.stackoverflow.com

• 440 questions asked
• 326 questions with a score of 0 or greater
• 115 answered, 35% answered rate
• 182 replied, 56% reply rate

Since last Wednesday’s update, we announced the built-in follow action, shared guidance on how to grow mobile games and apps with Facebook, and announced plans to help you stay connected to other Facebook developers with Meetups.

Adding multiple photos and location to Open Graph actions

Photos and places are important for helping users tell rich stories. As such we’ve now added the ability to attach multiple photos to Open Graph actions and have added better location support. You can now associate your own location data with your Open Graph actions and objects. This means that you can create your own place objects or use a third party location service instead of Facebook place IDs. Stories that include a location will appear on a user’s Timeline map and will be included in their News Feed stories and aggregations.

To take advantage of this expanded location functionality, in your app’s Open Graph settings, select “place” from the drop down menu when defining an object and specify the location property with the “GeoPoint” type. You must also select the “places” checkbox when you submit your action for approval. There may be scenarios where you want to rely on third-party location services like Foursquare to attach location data to your actions. We will now accept third party locations and treat them appropriately.

Check out our documentation to learn more about publishing multiple photos for an action and tagging locations in actions.

New summary count fields in event FQL table

We’ve added the following fields to the event FQL table to make it easier to get the counts of users RSVP-ed to an event:

• all_members_count
• attending_count
• unsure_count
• declined_count
• not_replied_count

For more informations, check out the event FQL table documentation.

New date for offline_access permission removal

We were originally planning to remove the offline_access permission next week but have moved that change back to October 3rd, 2012. The Developer Roadmap has been updated. Please see the Removal of offline_access permission doc for more information.

Next week’s breaking changes

Several breaking changes will be going into effect next week on Thursday, July 5th. Normally, per our Breaking Change policy, we only introduce breaking changes on the first Wednesday of the month but July 4th is a U.S. holiday. Please review this list of changes to ensure your app is up to date and will continue working after we make these changes next week.

Changes without migrations

• Removing FB.Canvas.setAutoResize
• Event GETs from Graph API/FQL will require an access token

Changes in “July 2012 Breaking Changes” migration

• Removing display=wap dialogs
• Removing some event FQL object fields
• Coordinate-less tags
• Removing bookmark.add and profile.addtab dialogs
• Moving “type” property into “metadata” array

Changes in other migrations

• Removal of FBML
• Updating Page “hours” property
• Batch API exception format
• Removing timezone from event times

For the full details on all these changes, please check out the Developer Roadmap.

September migration now available

The “September 2012 Breaking Changes” migration is now available for you to test your apps to see if they will be affected by the breaking changes happening on September 5th, 2012. Check out the Developer Roadmap for more information on what changes are included in the migration.

Check your privacy policy

It is critical that people have a clear understanding about how the information they share with apps is used. As outlined in our policies, every app on Facebook must provide the URL to their privacy policy in the Dev App.

Starting next week, we will send weekly warnings via email to the developers of apps that have do not have a live privacy policy URL listed in the Dev App. If you have not resolved the issue by the third warning, your app will be placed into sandbox mode and users will not be able to access it. To get your app out of sandbox mode, you will need to go into the Advanced Dialog tab of the Dev App and add the URL to your privacy policy.

Javascript SDK cleanup

We are continuing to reduce the number of methods exposed by the global FB object in the Javascript SDK and will now start to log a warning to the console whenever a non-documented method is used. At a later time, these will all be stubbed with empty functions before finally being removed entirely from the FB object. For the list of publicly available methods, please see the Javascript SDK documentation.

Weekly Stats

The following stats are for activity between Wednesday, June 20th and Wednesday, June 27th.

Bugs activity

• 183 bugs were reported
• 24 bugs were reproducible and accepted (after duplicates removed)
• 11 bugs were by design
• 6 bugs were fixed
• 43 bugs were duplicate, invalid, or need more information

Bugs fixed

• Documentation typo: “setting setting the overflow property” on http://developers.facebook.com/docs/reference/plugins/like
• FB.Canvas.setSize does nothing in IE7 Page Tabs
• App Center Page “cover image” will not update in preview
• WordPress Plugin – Comments plugin width cannot be configured
• Error 500 occurs frequently during authorization when using facebook.com/device API
• Javascript API from Android/iPhone WebView does not work

Activity on facebook.stackoverflow.com

• 487 questions asked
• 356 questions with a score of 0 or greater
• 121 answered, 34% answered rate
• 215 replied, 60% reply rate

Since Last Wednesday’s update, we published a game spotlight on Candy Crush Saga, announced updates to the Facebook SDK for iOS , revealed the Toronto HACK Winners and introduced subscriptions and local currency pricing

Easier notification controls for users

We’re introducing a way for users to opt out of notifications from apps, groups, or other sources (photos, etc.) directly from the notifications drop down menu. People have always been able to opt out on the Notifications Settings page, but this update makes it easier.

People will see more notifications from the apps, groups and features they engage with most, and none from those they choose to remove. For app developers, a less cluttered drop down menu means that notifications from high quality apps will stand out more. Early results have shown that apps that send high quality notifications have seen a lift to click-through and revenue with this update.

You can monitor and improve your opt-out rate for notifications with a new dashboard in Insights. This does not change the way users receive updates from apps through channels like news feed and App Center.

Updates to the Javascript SDK

As announced in May, we have updated the Javascript SDK to limit the publicly exposed interface. This is part of an ongoing process to improve the reliability of the SDK.
We have removed access to all internal properties and to methods prefixed with _.

If you are currently relying on accessing internal properties, please refactor this so that you only rely on the publicly available (and officially supported) methods listed at https://developers.facebook.com/docs/reference/javascript/.

Note that all methods not listed as part of the public API might be subject to change or removal, and you should not use them directly.

July 5th 2012 Breaking Changes

Removing FB.Canvas.setAutoResize – Originally scheduled for January 1, 2011

We have renamed FB.Canvas.setAutoResize to FB.Canvas.setAutoGrow so that the method more accurately represents its function. FB.Canvas.setAutoResize will stop working on July 5th. We will completely delete the function on August 1st.

Event GETs from Graph API/FQL Will Require an Access Token

All calls to get events from the Graph API or FQL will now require an access token to be used.

Removal of FBML
FBML apps will no longer work on Platform. All FBML endpoints will be removed and the “FBML Removal” migration added June 6th will be removed.

September 2012 Breaking Changes (90-day notice)

The following changes can all be enabled/disabled using September 2012 Breaking Changes migration (will be available in the next 7 days) until September 5th when they will go into effect permanently for everyone:

Removing Live Stream plugin
The Live Stream plugin will be removed on September 5, 2012. We recommend using the Comments Box plugin instead. Please migrate your app as soon as possible. On September 5th, if your app is still using the Live Stream plugin, we will render the Comments Box plugin in its place. While it offers similar functionality, there are a few functional differences. Please see the Live Stream plugin documentation for more info.

Renaming ‘likes’ property of Comments and ‘votes’ property of QuestionOptions

We will be renaming the likes property of the Comment object to like_count and the votes property of the QuestionOption to vote_count.

Minor change to admin.getAppProperties call
When making an admin.getAppProperties call, we will now return an empty iOS Bundle ID as [] instead of [""].

Returning actual size in photo_src table
We will start returning the actual size, height, and width of photos in the photo_src FQL table instead of the dimensions of the bounding box.

Bugs activity between Wednesday, June 13 and Wednesday, June 20

• 167 bugs were reported
• 36 bugs were reproducible and accepted (after duplicates removed)
• 7 bugs were by design
• 17 bugs were fixed
• 73 bugs were duplicate, invalid, or need more information

Bugs fixed between Wednesday, June 13 and Wednesday, June 20

• oauth dialog is completely broken
• no data scraped, can’t like, can’t set as website for app
• Very slow API response time
• Send Dialog: send button disabled in Firefox
• Like Box width too wide
• can’t select “Native Android App” option
• Comment plugin for mobile users does not fold out more comment
• Send button on FB.ui dialog can be pressed with ‘To:’ form empty
• Any Page Tab App shows CSS instead of content or asks to download page_proxy.css
• credits dispute notification emails have stopped being sent.
• OpenGraph built-in action ‘required’ but lacking flexibility
• Comments report shows 0 comments on insights after may 9th.
• Allow Pages To Comment On Comments Plugin
• not able to post comments on content using only publish_actions permission
• using the “offer” pay dialog breaks FB.Canvas.getPageInfo
• FB.login dialog will hung after click ‘Log In’ in IE.
• Social Plugins Applications selector to short

Activity on facebook.stackoverflow.com between Wednesday, June 13 and Wednesday, June 20

• 475 questions asked
• 340 questions with a score of 0 or greater
• 123 answered, 36% answered rate
• 213 replied, 63% reply rate

Since last Wednesday’s update, we spotlighted NBC’s The Voice, published Early Success Stories: Shopping, Fashion and Open Graph, and published a Games Round-Up.

Breaking Changes Effective Today

Today the following changes are in effect. For more information, check out the Developer Roadmap.

Removal of FBML
FBML apps will no longer work on Platform. The “FBML Removal” migration now appears and is enabled for all apps. It will be possible to disable the migration, thereby re-enabling FBML, until July 5, 2012 when the migration and all FBML endpoints will be removed completely.

XMPP Connections must be done over TLS
Apps connecting to Facebook’s XMPP service should now use STARTTLS for all connections. We have started rejecting unencrypted connections.

September 2012 Breaking Changes (90-day notice)

The following changes can all be enabled/disabled using September 2012 Breaking Changes migration (will be available starting June 13th) until September 5th when they will go into effect permanently for everyone:

Removing Live Stream plugin
The Live Stream plugin will be removed on September 5, 2012. We recommend using the Comments Box plugin instead. Please migrate your app as soon as possible. On September 5th, if your app is still using the Live Stream plugin, we will render the Comments Box plugin in its place. While it offers similar functionality, there are a few functional differences. Please see the Live Stream plugin documentation for more info.

Renaming ‘likes’ property of Comments and ‘votes’ property of QuestionOptions

We will be renaming the likes property of the Comment object to like_count and the votes property of the QuestionOption to vote_count.

Minor change to admin.getAppProperties call
When making an admin.getAppProperties call, we will now return an empty iOS Bundle ID as [] instead of [""].

Returning actual size in photo_src table
We will start returning the actual size, height, and width of photos in the photo_src FQL table instead of the dimensions of the bounding box.

Bugs activity between Tuesday, May 29 and Tuesday, June 5

• 178 bugs were reported
• 42 bugs were reproducible and accepted (after duplicates removed)
• 9 bugs were by design
• 54 bugs were fixed
• 193 bugs were duplicate, invalid, or need more information

Bugs fixed between Tuesday, May 29 and Tuesday, June 5

• Lost fans after migrating Application Profile Page in January/February.
• API responds extremely slow
• Unable to view app roles
• Hijacked Like Button (Facebook security technical problem, spam/scam)
• Undeleteable test users
• So called “bomb-like” exposes flaw with access tokens on query string
• Cannot change Native Language in App Center
• Can’t submit an action for my app
• Service Unavailable – DNS failure: missing crossdomain.xml in http://m.ak.fbcdn.net
• User Generated Photos option not being passed from step 2 to 3…
• App’s Custom Open Graph actions constantly flip from approved to pending
• Edit custom object fails
• Comment moderation – hiding comment doesn’t seem to work
• Requests Dialog Will Not Load
• Players receiving invalid timeline notifications
• Loop games notifications with Timeline ?
• Fatal error: Uncaught OAuthException: An unknown error has occurred. when doing fql event query
• No docs for photo upload with URL param
• Posts not appearing on News Feed after migrating to Timeline for Pages
• No “create new bug” button visible on start page
• Blocked applications posts are showing in news feed stream
• Broken test user
• Cannot link Paypal Account when registering a company from Brazil
• No ‘rejected’ comments for open graph action submit
• Contradicting communication, why can’t we ask for publish_actions?
• Facebook Like button shows the “Confirm” link
• Facebook fails to use app privacy setting when publishing links
• Add Page Dialog stopped working, causes error
• Problem with ‘Region’ in ‘Sign Up for Facebook Credits’
• Friends info doesnt return picture
• Album (Graph API) documentation – likes and comments “Returns” columns are swapped
• News feed publications generated from our app do not show
• YouTube Information is not being pulled in.
• Scraper sometimes fails to parse og:type
• traceroute to FB hosts failed, cannot pass tfbnw.net
• picture URL for /feed post not accepted if HTTPS
• featured music services: friends listening counter way off
• facepile iframe for some content returns facebook error page when showing action news.reads
• Link attachments in messages sent through the new messaging API don’t show up in mobile interfaces
• Opengraph
• Listen Button on ticker
• Facebook Object Debugger Returning “HBaseHashout”
• Date piping on Action not correct
• Online presence always ‘offline’
• Insights is showing 0 active users
• Map aggregation not working & map style selection inverted
• Subscription page lists ‘picture’ as a valid field for user.
• Add a parameter to align the Like button to the right
• PHP SDK Unknown SSL protocol error in connection to
• API search in japanese language do not returns recent results
• IE 7 comments plugin producing “Member not found” error
• Facebook URL Linter strippign trailing slash
• story and story_tag not documented on Post object
• fb_ref not included in timeline links

Activity on facebook.stackoverflow.com between Tuesday, May 29 and Tuesday, June 5

• 450 questions asked
• 381 questions with a score of 0 or greater
• 161 answered, 42% answered rate
• 265 replied, 70% reply rate