Migrate to Facebook Graph API V2 With a Push of a Button

Facebook has announced a new tool that helps developers migrate apps to Graph API v2.0 without any necessary code changes. Facebook's Graph API v2.0 was announced last April, and all apps that have integrated the API will be automatically upgraded to v2.0 on April 30. The tool takes the form of a button that enables an app to use v2.0 by default. Developers turn the button on and off at the Migration tab of an app's Setting page.

Late last year, Facebook gave developers the ability to test how apps would behave after the upgrade to v2.0. Many developers tested the change and offered feedback. Developers expressed the desire to simplify the migration. Namely, developers preferred a migration path that would eliminate the need to write new code and redeploy the app. Facebook responded with the release of the button with a little over two months before the automatic switch to v2.0.

After turning the button on, a number of changes will arise. First, an app user will see the new Facebook login dialogue, which gives the user greater control over information shared. Second, only permissions available in v2.0 will be seen in the login dialogue. Next, a user who logs in will be known by an app-scoped user ID. Finally, a new call, /me/friends will return the user's friends who also use the app. For a full list of changes, visit the changelog. Utilizing the button will make the same changes that will take place after the automatic migration on April 30.

Facebook suggests developers refrain from using the button if their apps utilize features that have been changed or deprecated in v2.0. For a full list of changes and deprecations, visit the changelog. For developers who continue to rely on features soon to disappear, Facebook suggests a manual update.

Developers provided candid feedback on the migration to v2.0 and Facebook has responded. Upgrades can now proceed with the simple push of a button.

Be sure to read the next Social article: Facebook Graph API Bug Exposes Vulnerability

 

Comments (0)