The social network introduced the updated application-programming interface at its F8 global developer conference last April, and this past December, it released a tool that allowed developers to preview how their applications will perform after upgrading their APIs.
Last December, we added the ability for you to use test users to see how your app will behave against Graph API v2.x without having to update your code. Many of you tested your apps and gave us the feedback that you’d like a simple way to take the next step: to upgrade without having to write code and redeploy. Now, we are launching a button that allows your app to use Graph API v2.0 by default.
To make the change, go to the migrations tab of your app’s settings page. You can switch the “Use Graph API v2.0 by default” setting to on (or off to revert your app back to its original state).
Here’s what will happen after you enable this migration:
- People who log into your app will see the new Facebook Login dialog, which gives them greater control over what information they share. This means people will be able to decline to grant one or more of the permissions you’re requesting.
- Only the permissions that remain available in v2.0 will be shown in the login dialog and be useable when making API calls: e.g. the friends_birthday permission will not be grantable, and API calls that use this permission may return empty arrays.
- People logging into your app for the first time will be known by an app-scoped user ID. Note that if you enable and then later disable this migration, people who first logged into your app while the migration was enabled will still be known by the same app-scoped ID after the migration is disabled.
- Calls to /me/friends will return the user’s friends who also use the app.
This is the same set of changes that will come into effect for all apps April 30. For the full list of changes, please see the change log.
If your app relies on some of the features that have changed or been deprecated in v2.0, we suggest that you do not enable your migration using this new tool, and instead manually update your app to call Graph API v2.0 or above. With the migration date only a few weeks away, we advise you to begin making these changes now. For more information on how to upgrade to v2.0, please see the upgrade guide.
But if your app is already able to handle these changes, or if you’re not using features that have changed, you can now instantly upgrade your app with the flick of a switch.
Developers: Are you ready for Graph API v2.0, or will you be ready by April 30?