URGENT - Facebook Developers App Update Notice - what to do?

[J.Wings]

Got this on facebook today for 2 of my network apps so far...

Your app, OPM - Original Pinoy Music, needs to be updated for the February 2013 Breaking Changes.

Once your app is compliant, set the migration setting to "Enabled" in the Advanced section of the App Dashboard.

These changes will be permanently enabled for all apps in 1 day on Tuesday, February 5, 2013.

UPDATE: Got a VERY helpful response from Ning below and just wanted to put it here to save people digging through the comments in a panic:

Reply by Allison Leahy (around 9:15pm pacific time)

Just got this message myself and went through the flow. I'll publish a tutorial replete with screenshots and a brief overview of what Facebook's been up to and why they require this compliance shortly. If you just want to get it over with, follow these steps:

Head to your Facebook Developers page, log in, select your app, click "Edit Migrations," scroll down to the Migrations section, select the "enabled" radio button next to "February 6th Breaking Changes" and click "Save." 

UPDATE 2 - The tutorial to solve the issue is linked here:

 February 2013 Breaking Changes tutorial

[J.Wings]

can someone from ning please address this in terms of letting us know what will break and what we need to tell our users? Im relatively sure that whatever needs to happen cant happen by tuesday, so just help me know what to expect.

Is anyone else getting these? Maybe im crazy and its just me?

[Chris]

Apparently we only have one day to fix this. I don't even know if there's anything to fix... I think we have to manually "set the migration setting to "Enabled" in the Advanced section of the App Dashboard." for our apps, but again I don't know if we have to ourselves or if Ning does.

[J.Wings]

Yeah this sounds like a typical Facebook BS move. Announce something at a conference then change the whole system a few days later and give people no time to deal with it. I can totally sympathize with Ning on this if it ends up being the case that all of our apps are waxed. How could they possible come up with a solution in 2 days? They probably cant even have a meeting to talk about what the issue is until after lunch on Monday, in the best possible scenario. 

The question then becomes... Can users still sign in through FB? Do the social sharing buttons work? Can Ning fix it alone or is there a step that needs to happen where creators go in and update the settings AFTER Ning changes the code...?

[Chris]

Sounds like a right headache. I'll share this discussion with my friends so it's up front tomorrow morning, and maybe one of them will know something...

[Allison Leahy]

Just got this message myself and went through the flow. I'll publish a tutorial replete with screenshots and a brief overview of what Facebook's been up to and why they require this compliance shortly. If you just want to get it over with, follow these steps:

Head to your Facebook Developers page, log in, select your app, click "Edit Migrations," scroll down to the Migrations section, select the "enabled" radio button next to "February 6th Breaking Changes" and click "Save." 

[Scott Bishop]

Okay, did it. Do you think that we'll need to do anything more?

[Allison Leahy]

I think that should do it. 

[J.Wings]

Thanks for devoting some of your Sunday night to this :)

[J.Wings]

Especially considering all of us San Franciscans should be out drinking after the Stupid Bowl ;)

[Allison Leahy]

Beyonce Bowl! 

[Chris]

Thanks Allison. Do any of these migrations require code changes in the app, or is it as simple as "enabling the migration" each time over the coming months for each application?

[Allison Leahy]

No need to update anything else.