CoderTakeout - Facebook Development

The issues with JS SDK should now be resolved.

Currently, the JS SDK is returning /* Not a valid locale. */. We are working on a fix now. We will update the live status as we have more information. You can following along in https://developers.facebook.com/bugs/203275643103137

Please note that we are currently seeing issues with creating and updating adgroups using the 'redownload=1' option. We are working on resolving this as a matter of urgency. If you are encountering this issue you can work around it temporarily by removing the 'redownload ' parameter from the request.
For more information and updates, please subscribe to https://developers.facebook.com/bugs/230460137038455

As announced on the blog on July 29, 2011 and on the Roadmap, to read or manage a user's notifications we now require the "manage_notifications" permission. The "Require manage_notifications" migration has now been removed per our 90-day breaking change policy. For more information, see the User object documentation.

We are currently investigating issues with the bug tool.

The issues with the PHP SDK and OAuth should now be resolved.

We're investigating issues using PHP SDK OAuth flow causing failed validation. We will post here and on bug http://developers.facebook.com/bugs/220904677985962 when we have this issue is resolved.

As part of our commitment to migrate all apps to OAuth 2.0, we are opting in all apps using the new JavaScript SDK to OAuth 2.0. The deadline to support OAuth 2.0 was October 1st, 2011. The new JS SDK with OAuth 2.0 was introduced in July. We are now automatically defaulting the oauth param to true in FB.init. With this change, please ensure that you are using FB.getAuthResponse to obtain the access token. Read more about the specific changes that you need to make here: https://developers.facebook.com/blog/post/525/

As part of our continued efforts to migrate all apps to Oauth 2.0, we opted in all apps using the new JavaScript SDK to OAuth 2.0 this afternoon at 11am PT and are now reverting (ETA 1:30pm). This means that the oauth:true param in FB.init will be set to true by default. With this change, please ensure that you are using FB.getAuthResponse to obtain the access token. Read more here: https://developers.facebook.com/docs/oauth2-https-migration/ or visit our JS SDK documentation.

If your app was affected, please ensure that you have made these upgrades by next week.

As part of our continued efforts to migrate all apps to Oauth 2.0, we opted in all apps using the new JavaScript SDK to OAuth 2.0 this afternoon at 11am. This means that the oauth:true param in FB.init will be set to true by default. With this change, please ensure that you are using FB.getAuthResponse to obtain the access token. Full documentation available here: https://developers.facebook.com/docs/reference/javascript/

As a reminder, we are also removing the old JavaScript library (FeatureLoader.js) and the old iPhone SDK (facebook-iphone-sdk) for authentication. Please ensure that you are no longer using these non-OAuth libraries. Users will not be able to authenticate with your app.

Since we noticed a service disruption on some apps, we have reverted this change, but will attempt to do this again next week.