Firebase auth with Facebook just stopped working on all our Polymer websites. One of them where updated 19th of march and has been working until yesterday/this afternoon (2017-03-27).
I get the following error message in chrome:
firebase-auth.js:32
"{"error":{"errors":[{"domain":"global","reason":"invalid","message":"A system error has occurred"}],"code":400,"message":"A system error has occurred"}}
Firebase Authentication is having problems right now. Look at the Firebase Status Dashboard here:
https://status.firebase.google.com/
Graph API v2.2 has reached the end of its 2-year lifetime on 27 March, 2017, so this might be connected. You should check your library and possible updates. See this chart of deprecation dates, which lists v2.2 as available until March 25, 2017.
Related
We have a data pipeline for our Facebook app events data. Is there any alternative solution for getting the facebook export data as it is deprecated and will stop working from Aug 1st 2018?
https://developers.facebook.com/docs/analytics/export
The Export API is deprecated and will stop working on August 1st 2018.
Our site have integrated registration and login through facebook using facebook regsitration plugin as described in url https://developers.facebook.com/docs/plugins/registration/v1.0.
Recently 3 months back we upgraded Facebook API to version 2.2 but kept our registration plugin to as described in above url and it worked well. But today we noticed that facebook registration plugin control is not working. It is throwing following error
Unable to load the registration form. You may have previously blocked
this app on Facebook. Go to your Facebook privacy settings to unblock
this app. (Error: 404)
We did some research and find the url https://developers.facebook.com/docs/plugins/registration/v2.2 which states that this registration plugin control will stop working after 30th July 2015. But not sure why it has stopped working before that day.
Can any one please let us know why this error is coming? And also what is the resolution for this issue?
As stated in the doc:
The Registration Plugin is deprecated and will be removed on April 30,
2015. You should not integrate this plugin into new apps. If you're using this plugin, you should replace it with Facebook Login before
April 30, 2015
Even if this were a bug it is highly unlikely that it will be looked into since it is deprecated.
The only resolution is to migrate to Facebook Login as suggested in the warning message.
According to Twitter API FAQ,
REST API version 1 is now deprecated and will cease functioning in
March 2013. Move to version 1.1 as soon as possible. The concept of
"version 1" of the API includes unversioned APIs like the Search API.
However, at the moment it is still working. For example, you can still search for tweets. Will the legacy API finally cease working, and if it will, when will that happen?
The Twitter API v1 will be retired on June 11th 2013.
Full details at the link below:
https://dev.twitter.com/blog/api-v1-retirement-date-extended-to-june-11
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.
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.