facebook api version

the facebook auth uses graph api 2.3 which will be EOL on 8th of July 2017.

the current version is 2.8
see https://developers.facebook.com/docs/apps/changelog?locale=en_US

would be great to use a more recent version so people upgrading this package in the near future will be safe for a longer time

Well that matter is pertinent because I afraid if I force a higher version, it may break the current applications.

I can just remove the version number from the dialog URL and it will use a version which I am not sure if it is the highest or the minimum.

Anyway applications can call the API with any version they want. I am just not sure if the dialog URL version is relevant.

What do you think?

When I saw all the v2.3 calls in the sources, I was a little concerned, too. But according to https://developers.facebook.com/docs/apps/versions :

"For APIs, once a version is no longer usable, any calls made to it will be defaulted to the next oldest usable version. Here's a timeline example:"

That page says that a particular version becomes unusable exactly two years after the subsequent version is released. According to https://developers.facebook.com/docs/graph-api/changelog/archive , version 2.3 became unusable on July 8, 2017. And version 2.6 became unusable as of July 13, 2018. As of today (September 5, 2018), the oldest usable version is 2.7, which will become unusable as of October 5, 2018. So any code that today specifies a Graph API version between 1.0 and 2.6 will wind up using version 2.7. And on October 6, that same code will wind up using version 2.8.

So specifying an explicit version in the code effectively specifies the minimum version to be used, which means that the OAuth library sources are doing the right thing, and should only break when/if facebook makes seriously-breaking changes. I didn't find anything stating what (if anything) they do if the "next oldest usable version" just doesn't support the Graph API request from the explicitly requested version at all.