My app has is no longer allowing people to post to facebook from it, and it is throwing this error when I try -
"Error: This endpoint has been deprecated. To temporarily enable it, you may disable the "august 2012" platform migration. It will be disabled permanently on August 1, 2012."
I read a couple of other posts from people having the same issue, and attempted to fix it, by disabling August 2012 Breaking Changes. It was already disabled though, and I have been unable to find any other way to fix the problem.
Any idea how to fix it?
When Facebook make changes to their API, they're offering a migration period of 90 days for the developers to migrate.
But if you haven't migrated after that grace period, you're pretty much screwed.
These are the breaking changes from August 2012:
Disabling FB.Canvas.setAutoResize - Originally scheduled for January
1, 2011 We have renamed FB.Canvas.setAutoResize to
FB.Canvas.setAutoGrow so that the method more accurately represents
its function. FB.Canvas.setAutoResize will stop working on August 1st.
We will completely delete the function on September 5th.
Page Post GETs from Graph API/FQL Will Require an Access Token
All calls to GET Page posts from the Graph API or FQL will now require an
access token to be used.
Removing prompt_permissions.php and prompt_feed.php
We will be removing a very old version of the feed dialog
(/connect/prompt_feed.php) as well as a very old version of the auth
dialog (/connect/prompt_permissions(s).php). If you are one of the
very few developers still using these legacy endpoints, you should
upgrade to the current Feed Dialog and/or OAuth Dialog.
Removing Add To Timeline Plugin
We will be removing the Add to
Timeline plugin. If you are embedding the Add to Timeline plugin, we
will render the Login Button in its place with the publish_actions
permission automatically added to the scope parameter.
I can't tell which change that broke your app (though I'm guessing it's Removing prompt_permissions.php and prompt_feed.php), but you should make sure to update to the latest version of any Facebook framework (i.e. update ShareKit) you're using and/or make sure to use the new Facebook API ASAP.
To avoid similar issues in the future, be sure to watch the roadmap and - even better - follow the developer blog.
Related
I am trying to connect a facebook app but it is displaying error as "Can't Load URL: The domain of this URL isn't included in the app's domains. To be able to load this URL, add all domains and subdomains of your app to the App Domains field in your app settings."
the domain i am using is https://app.streamlivve.com
I tried all of solutions but nothing happen. here is my settings of FB app page
Can you please guide me to solve this error:
Facebook announced in Dec 2017 that in March 2018 they would change the settings for Oauth redirects:
https://developers.facebook.com/blog/post/2017/12/18/strict-uri-matching/
In a nutshell, you can only redirect to explicit, precise pre-determined URIs now. Which is annoying if (like me) you want to pass URI parameters back as well...
Make sure you're using Facebook SDK 5.6.2. There was an important fix.
Since this March (started running a couple of days ago), strict mode is now enabled by default. This means you now need to have the exact redirect URLs you're using marked as such in the app configuration.
You can see more here about what this entails and how to get on with the change.
Further, you need to update your dependency to version 5.6.2, as there's a bug in the previous version that wouldn't work with strict URI matching (yes, the one that is now enabled by default), so the login would break. You can see more about the fix in the pull request that fixed it. I can confirm that updating to 5.6.2 (PHP) fixed the issue.
To update your version in PHP, it depends on which expression you have in your composer.json, but if you have "facebook/graph-sdk": "^5.6", for example, a simple composer update will suffice.
I notice Facebook makes changes every so often. For example, it's html page structure changes every so often (if you write a like count scraper, then all of a sudden your scraper is broken one day).
Also I noticed URLs of the form https://www.facebook.com/video.php?v=100000000000000 started redirecting to https://www.facebook.com/{pagename}/videos/100000000000000 .... Probably the redirection will stay the same but I wonder - does Facebook publish these changes in behavior or how do you keep up with them?
I wasn't even sure this was the right place to post but I couldn't find a facebook stackoverflow community....Thanks!
If you build functionality off the Graph API there is a changelog, and versioning support e.g. you can build against a specific version and keep using functionality even though it is removed in later versions.
https://developers.facebook.com/docs/apps/changelog
Here is the notification I just received:
App, is currently using the following deprecated features:
Non-threaded comments. Please see the developer roadmap for more details about this change.
I looked all over the API and the developer roadmap and the settings but found no way to fix this issue. How do I fix this?
My hunch would be that they send out alerts based on the permissions your app uses - my app doesn't interact with any "comments" connections in the graph, but it does have the "publish_stream" and "manage_pages" permissions.
If someone knows otherwise please advise...
I have received the same notification for one of my apps. My app definitely does not read or create comments on Facebook posts or objects (Facebook rolled out the threaded comments Feature in April). Thus Facebook's message is not relevant to every app they send it to.
The change should only affect apps which read or publish comments.
Here is the link to the API documentation about comments:
http://developers.facebook.com/docs/reference/api/Comment/
Look at the settings page, in the "Migrations" section. Enable "July 2013 Breaking Changes" and your notification should have a green sign notifying: Your app, appname, is now compliant with the July 2013 Breaking Changes migration. No further action is required.
Be sure to read the complete roadmap at https://developers.facebook.com/roadmap/.
I have got the following message too:
MyApp, is currently using the following deprecated features:
The 'page_id' field in the checkin FQL table. Please use 'target_id' instead.
The 'version' field in the group FQL Table and on the Graph API.
Non-threaded comments. Please see the developer roadmap for more details about this change.
I am sure that in my case the warning derives from my Graph API Explorer and
my Django test code.
That means that Facebook logs every request sent by your App and send you a warning even if you used deprecated features only once.
Check it out
I have been trying to connect my Facebook Page to my Twitter account along with my regular Facebook page.
It links to my regular page fine...but Everytime I check my Facebook Fanpage it gives me this error:
ERROR: This endpoint has been deprecated. To temporarily reenable it, you may disable the "august_2012" platform migration. It will be disabled permanently on August 1, 2012.
I'm not a programmer. I have looked everywhere to try to "Diasable" this and cannot find where to do this. When will this be fixed on Facebook/Twitter's end?
I'm afraid this will never be fixed.
Facebook platform is a living environment - it means new stuff is added to it and some stuff is also removed. It seems the functionality has been removed. Since it is already past 1st August it is gone for good.
I just got this email from Facebook:
Dear Developer,
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 reverted at 1:30pm because we noticed that
your app has not migrated. Please ensure that you have set the oauth
param in FB.init to true and that you are using FB.getAuthResponse to
obtain the access token.
Read more in the OAuth2 migration announcement, updates to the new JS
SDK blog post, or our JS SDK docs.
If your app was affected today, please ensure that you have made these
changes by December 13th, 2012 to avoid any disruption with your
users.
The email doesn't specify which app needs my attention, and I can't make heads or tails of it.
Can anyone tell me what I need to be doing here? I have seven apps:
Four were created solely because I needed an app ID (API key) to install the "Like" button on various sites. Do I need to add "oauth: true" to the FB.init() call on these pages? (None of them actually integrate with Facebook authentication. All they do is render Like/Send buttons, and hook into the Edge.create callback for tracking purposes.)
Two of my apps are just tabs that I've added to Facebook Pages, which pull in static HTML pages (hosted elsewhere) via iframe. There's no JavaScript or server-side code whatsoever. I presume I can leave these alone?
One is an off-the-shelf app from a third-party provider. Looking at their code, I see that their call to FB.init() already includes oauth: true.
Facebook does a really terrible job with developer documentation, explaining changes, and maintaining backward compatibility. I'm a pretty experienced developer, but it seems like you have to learn every nook and cranny of Facebook's (ever-changing and over-complicated) proprietary API suite just to use the simplest features. I'm not a Facebook app developer (and I don't want to become one); I'm just a guy who wants to use a few "Like" buttons and custom page tabs, preferably without having to wade through this nonsense every two months when Facebook decides to change everything around and break backward compatibility again.
Anyway, any guidance would be much appreciated!
If you didn't see any of the blog posts since May - here's a summary: https://developers.facebook.com/docs/oauth2-https-migration/
To answer your specific questions, the 4 apps used only for the social plugins don't really USE oauth - but adding the oauth:true param and making sure they still work shouldn't be a huge issue - it also explicitly indicates to facebook that you're using the new auth mechanisms on those app IDs, so you shouldn't have an email sent about those apps in future
If your other apps aren't actually using any authentication, you probably don't need to do anything - if there was a problem you'd have discovered it yesterday when the oauth migration was flipped on for apps - the non compliant apps would have ceased working correctly