I'm working on Rails app using Facebook Graph everything was working fine and then suddenly images stop loading for user_pages, i debug and found the following error,
{
"error": {
"message": "The 'manage_pages' permission must be granted before impersonating a user's page.",
"type": "OAuthException",
"code": 190
}
}
Any idea why it start happening. Please see attached screen-shot
Thanks
30th April was the last date when Facebook stopped supporting older versions of the App. I am not 100% sure but it seems you need to go to your developer account and submit a review request for your app with additional permissions.
It seems you missed the news on Facebook's API upgrade - just like me. More information here: https://developers.facebook.com/docs/apps/api-v1-deprecation and https://developers.facebook.com/blog/post/2015/04/28/april-30-migration/
Related
I've created a medium application for API access a while ago, and I've been using it to connect medium accounts to my website and let them publish stories from my website. But it stopped working recently, and I can't access my app anywhere. I should mention that my medium account isn't premium, so I've been thinking that's the problem. The thing is I can't find any info anywhere about medium preventing free users from creating apps. This is where I've managed my apps in the past: Link, but now I get 403. Does anyone have any info about this?
edit: What I forgot to say is, when I try to connect my account, I receive the access/refresh token, but then when I try the "https://api.medium.com/v1/me" endpoint I get
{
"errors": [
{
"message": "Application not found",
"code": 6005
}
]
}
We have just run into a new bug with our app, which has been working for months. Whenever new users come to the app to try to sign up (through Instagram) Instagram responds with this error:
{"code": 400, "error_type": "OAuthException", "error_message": "User has revoked access to this client"}
Of course, prior to this, the user grants the app access. So how could it be revoked? We have also checked with test accounts, and verified that the app does indeed have access by looking it up in settings.
There were a number of people (including us) on Stack Overflow experiencing issues a few days ago with Instagram OAuth, which appeared to have been resolved.
Is this a widespread issue? Is anyone else experiencing this or is it limited to our app?
I am using the below url for getting the share count for twitter
https://cdn.syndication.twitter.com/widgets/tweetbutton/count.json?url=google.com
It is working finee before yesterday then sudden its get broken and I am getting below response from twitter when calling above url
"errors":
{
"message": "Sorry, that page does not exist",
"code": 34
}
Then I have also tried below url for getting share count
https://cdn.api.twitter.com/1/urls/count.json?url=www.google.com
http://urls.api.twitter.com/1/urls/count.json?url=www.google.com
It also result in same error
Please anyone can help me how can I get the proper share count in twitter, And I am not so good in English I apologies for that
Twitter disabled this feature a few days ago that's the reason why it is not working anymore.
You can find more information by reading this blog post.
Twitter shut down this API, but you can get an alternative at http://opensharecount.com
I am trying to do a simple translation using Google Translate in my iOS app but as i call the url, i am getting the following error in response…
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "accessNotConfigured",
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
],
"code": 403,
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
}
I couldn't find anything close to any solution of this issue.. Please can anyone help here. thanks in advance…
Well after some detailed searching and RnD, i found out that Google Translate API doesn't work with Bundle Identifier in iOS.. People have filed it as a bug on google forums.. So anyone trying hard to solve this can stop the efforts till it is solved..
You need to set ON for the Google Translate API.
Read 3rd step of setup of Getting Started link.
In the sidebar on the left, select APIs & auth. In the list of APIs, make sure the status is ON for the Google Translate API.
And make sure have to enable billing?
Important: Google Translate API v2 requires billing information for all accounts before you can start using the service.
And also have to set API key in proper way?
Since bundle id is optional for Key. So you can escape adding bundle id and enable the billing on. It will work. Try and let me know.
This error comes when you hadn't add the Credit card detail with your Google Cloud account, as rules has changed in which you need to add credit card details if you use Google translate api.
I'm using gem omniauth-google-oauth2 to login with google from Rails app.
These days I'm getting this error:
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "accessNotConfigured",
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
],
"code": 403,
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
}
Same settings would work fine for localhost, but failed frequently and sometime work on production. I have no idea of what's going on? Is Google changing there API recently? What API do I need to enable just to login and get user info?
I came across this problem when updating from omniauth-google-oauth2 0.2.2 to 0.2.4. To resolve the issue, go to your Google Developers Console. Click on "APIs" and enable the "Contacts API" and "Google+ API". This GitHub issue describes the problem in more detail.
We're started experiencing the same issue 20 hours ago, but it's appearing on both production and localhost (which use two separate Google accounts). The strange thing is that we are able to log in every 3 or 4 tries, but not every time.
As far as an API change on Google's end, this issue on omniauth-google-oauth2 seems relevant: https://github.com/zquestz/omniauth-google-oauth2/issues/106. However, this deprecation should not be enforced until September, 2014.
Also, editing the omniauth-google-oauth2 gem directly and changing these lines:
class GoogleOauth2 < OmniAuth::Strategies::OAuth2
BASE_SCOPE_URL = "https://www.googleapis.com/auth/"
DEFAULT_SCOPE = "userinfo.email,userinfo.profile"
to this:
class GoogleOauth2 < OmniAuth::Strategies::OAuth2
BASE_SCOPE_URL = "https://www.googleapis.com/auth/"
DEFAULT_SCOPE = "email,profile"
Yielded this error:
Error: invalid_scope
Some requested scopes were invalid. {invalid=[https://www.googleapis.com/auth/profile, https://www.googleapis.com/auth/email]}
Update:
Quoted from an email from Lever (hire.lever.co):
"The issue stemmed from an bug in a release Google made to the authentication system Lever uses to identify users last night. We were among some apps who lost the ability to verify users via their Google OAuth API. We've been in communication with Google, and we've been told that the release was reverted at 11:30AM PDT."
Google OAuth appears to be fixed for us now.
We found that Billing had been enabled for one of our projects, but no Billing information entered. Disabling Billing for this particular project so far seems to have resolved this issue for us.
The error we were getting was:
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "accessNotConfigured",
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
],
"code": 403,
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
}
Update: Of course our fix was applied ~ 11:30 AM PDT, so I am I'm voting this was a Google issue.