Facebook Graph API v2.6 upgrade?

@Corona staff:

I just got this from Facebook:

Your App, [my app name], is currently accessing Graph API v2.5 which will reach the end of its 2-year lifetime on 12 April, 2018. We estimate 1 endpoint that [my app name] calls will be impacted by this change and may stop working after the automatic upgrade push. To ensure a smooth transition, please migrate all calls to Graph API v2.6 or higher. Use the API Upgrade Tool to understand exactly how this change will impact your app.

Will the Facebook v4a plugin be updated to meet these need demands?

I looks like the SDK we are using was released in August 2017. According to:

https://developers.facebook.com/docs/graph-api/changelog

Our plugin should be using Graph API 2.10 and we should be good. I got a similar message today.

Rob

Me too and it is older players… Nothing we can do if they don’t update.

According to Engineering we will be releasing a new FB plugin in a few days that goes to 4.31.0 of the FB SDK. This will raise the OpenGraph support to 2.12.  We should be all good to go with this warning from Facebook. But as @SGS points out, you will always have customers that don’t upgrade.

Rob

Ok, thanks for your answers! 

A bug report that I filed concerning problems with facebook.init() is possibly fixed in the v4a release you refer to above. One of your engineers emailed me about this and asked me to wait for the next version. Is there any way I can see when it has been released?

I’ve asked engineering to let me know what they fixed and when the update is available so I can update the community. It sounded like the bug fixes will happen pretty soon. I just don’t know what they are fixing at this time.

As far as updating to the new Facebook SDK, it appears that it has some changes in how facebook.request() works (new required parameters) so introducing it right now, doesn’t make sense. Likely we will hold that update until closer to the next public build.

Rob

Any updates on this?

The Facebook v4a plugin was updated on 3/17 with bug fixes. However it was not updated to the latest Facebook SDK because it would bring breaking changes to the actual Facebook calls.  We will apply the new SDK closer to the next public build.  However the current SDK is compatible with a modern Graph API and isn’t an issue with Facebooks message to update to 2.6 or later.  Even if you have older clients who haven’t updated recently who have a 2.5 compatible build, those API calls will be serviced by 2.6 and there are minimal changes between the two.

Rob

Great thanks!

Last question: do I need to download a new version of Corona to get the new version of the Facebook (or any) plugin? Or do I just need to rebuild the app?

Plugins are separate (usually) to Corona SDk so an updated plugin should “just work” with a new sim build

@Sphere Game Studios: thanks!

@Rob: I got an email from one of your developers, who said that the release on March 17 only was an “internal version” that is not publicly accessible. Some bugs in this version needed to be fixed before a “public release” can take place. Could you please just drop a note in this thread when the public release is here?   

@Rob: any news on the release date…?

No date yet. We don’t like to commit to dates because there are too many variables that can change it.  We have a lot of important tasks to address before the release and it’s hard to provide anything useful.

Rob

I looks like the SDK we are using was released in August 2017. According to:

https://developers.facebook.com/docs/graph-api/changelog

Our plugin should be using Graph API 2.10 and we should be good. I got a similar message today.

Rob

Me too and it is older players… Nothing we can do if they don’t update.

According to Engineering we will be releasing a new FB plugin in a few days that goes to 4.31.0 of the FB SDK. This will raise the OpenGraph support to 2.12.  We should be all good to go with this warning from Facebook. But as @SGS points out, you will always have customers that don’t upgrade.

Rob

Ok, thanks for your answers! 

A bug report that I filed concerning problems with facebook.init() is possibly fixed in the v4a release you refer to above. One of your engineers emailed me about this and asked me to wait for the next version. Is there any way I can see when it has been released?

I’ve asked engineering to let me know what they fixed and when the update is available so I can update the community. It sounded like the bug fixes will happen pretty soon. I just don’t know what they are fixing at this time.

As far as updating to the new Facebook SDK, it appears that it has some changes in how facebook.request() works (new required parameters) so introducing it right now, doesn’t make sense. Likely we will hold that update until closer to the next public build.

Rob