I have integrated Facebook API to get lead forms & leads, but few days ago leads service not working while lead form service still working.
Lead forms service (works fine and return lead count)
https://graph.facebook.com/v2.5/<form_id>?fields=id,leads_count&access_token=<token>
Leads service (Not working getting empty result)
https://graph.facebook.com/v2.5/<form_id>/leads?access_token=<token>
Thanks for your time
Related
So I made a bot using Bot Framework v4 Nodejs SDK and while the bot was healthy and running just yesterday. Today, something peculiar happened in the bot, only through facebook channel.
So whenever someone sends a message in the bot through messenger: the from object contains {"id":"3012023272144004","name":"FACEBOOK_USER_NAME"}
this is displayed in my code:
console.log("FROM DATA : " + JSON.stringify(stepContext.context.activity.from));
today it only displays {"id":"3012023272144004","name":" "} where the facebook name of user is always empty (and I assure you that users,that I tested, has a facebook name)
also whenever I request for facebook firstname and lastname using graph API I have this response
{"error":{"message":"(#80006) There have been too many messenger api calls to this Page account. Wait a bit and try again. For more info, please refer to https:\/\/developers.facebook.com\/docs\/graph-api\/overview\/rate-limiting.","type":"OAuthException","code":80006,"fbtrace_id":"AZp9laYMB2IGha-WAPYDBXH"}}
I retried it for the whole day, and nothing happened. I checked the dashboard for rate limit but all I can see is 0% limit used (the app is exclusively connected to my page and the page is exclusively connected to my app. thanks for the clarification)
and this never happened before, I always get the firstname, lastname, id and even profile picture - sample body response from previous calls:
{"first_name":"Nightshade","last_name":"Villabrille","profile_pic":"https:\/\/platform-lookaside.fbsbx.com\/platform\/profilepic\/?psid=2951340481545239&width=1024&ext=1586604925&hash=AeTsZ60vo4npjquO","id":"2951340481545239"}
I really have no idea where to ask this issue. Is this framework issue? facebook graph issue? or bot channels issue? Thanks!
---I'll provide code or respond to anything that I need to clarify. Thanks!
PS: Even other channels responds like this on email: {"id":"apvillabrille#up.edu.ph","name":"Villabrille, Aleimar P."} and webchat: {"id":"3012023272144004","name":"Web Chat User","role":"user"}
The Azure Bot Service change log is not currently available to the public, and the problem you experienced may not have had an entry in the change log anyway. It's unclear if the problem was on your end or Facebook's end or Microsoft's end, and if it was on Microsoft's end then it was more likely to have been a random outage than an actual code update. If your production bot experiences problems like this in the future then you can submit a support request through your bot resource in the Azure portal.
You might also consider engaging with the Facebook developer community: https://developers.facebook.com/docs/messenger-platform/useful-resources
I'm receiving reports of several users running into issues with a django-registration sign up flow. I'm not able to reproduce it, and I believe it's just happening for certain browsers.
The problem happens when they follow the email activation link. Although the database shows they have successfully activated their email, they see the page that says that the link has expired. It's as if they visited the activation page already and then are seeing it for the second time. Initially I thought this was user error, but several users have reported it, which makes me think there is something else up.
One user has reported it working in Firefox, but not Safari, on a desktop - and not working on iPad or iPhone.
I have used django-registration a lot so I'm surprised by this bug and am drawing blanks about what it might be down to. Anyone have any ideas?
PS This is also happening with the same site, perhaps related: Django messages faulty, but only on one particular network
I'm doing some kind of load testing with Facebook Test Java API for some app using fb authorization.
Since I'm doing selenium test in parallel, i'm able to see some effect:
I'm creating some test user
I get it's loginURL
I'm authorizing in selenium-driven browser with this loginURL
I'm creating many other users, each of them doing some stuff and becoming friend to the user from point 1, that is seen in selenium-driven browser.
At some moment I see this user logged off from facebook in browser. The exact moment is not clear, since the other test users are created and made friend with the target user in parallel threads, but it looks like this happens when i create 500 users.
When I try to log in again with loginURL obtained at step 2 it is still impossible. The fb redirects me to the login page.
It is possible to create much more than 500 users (at least 2000) with the api before the api will return the error, but the logging off is observed much before the reaching this limit.
The question is what is the limit of test facebook users supported with no problems?
And also, I've noticed that at beginning of the test test user access tokens worked okay, but by the end of the test all they were invalid and graph api didn't allowed to upload photos using that tokens.
Our desktop application integrates with Facebook using the desktop app workflow and for approx. 18 months has been working without any problems. However, we are starting to get reports from some users that they cannot get past the login process.
When the login is successful Facebook should be attaching the access_token to the redirect_uri. Our application detects this and moves the user to the main part of our Facebook integration. What appears to be happening in some situations is that the access_token parameter is missing which causes our application to leave our embedded browser window open with the following message from Facebook:
"Success
SECURITY WARNING: Please treat the URL above as you would your password and do not share it with anyone."
What is strange is that this does not occur with all Facebook accounts and which Facebook accounts it occurs with seems to be changing. For example, we had a report of this approx. 1 week ago but could not duplicate it with my own Facebook account or with a colleague's Facebook account. Today, I still cannot duplicate it with my own Facebook account but my colleague now gets the problem.
The URL our code sends to Facebook is:
https://graph.facebook.com/oauth/authorize?client_id=xxxx&redirect_uri=http://www.facebook.com/connect/login_success.html&type=user_agent&display=popup&scope=read_friendlists,user_photos,friends_photos,user_photo_video_tags,friends_photo_video_tags,user_events,friends_events,user_groups,friends_groups
Reading the latest API documentation it looks like they recommend a different way to connect which we have also tried:
https://www.facebook.com/dialog/oauth?client_id=xxxx&redirect_uri=http://www.facebook.com/connect/login_success.html&scope=read_friendlists,user_photos,friends_photos,user_photo_video_tags,friends_photo_video_tags,user_events,friends_events,user_groups,friends_groups&response_type=token
To rule out our application as the cause we have tried these URLs directly within a web browser. What we find is that when using my Facebook account the browser re-directs to the success URL that includes the access_token parameter but when using my colleague's account the browser re-directs to the success URL that includes the access_token and then immediately re-directs again to the success URL without the access_token.
so... As far as we can tell this is either:
a) A change to the API which we cannot find documented anywhere
b) A bug in Facebook
c) Something that is now controlled by the user's Facebook security settings
Is there anybody who could explain why Facebook is acting differently with different accounts and how we can go about fixing this?
Thanks.
Kevin.
I have the same problem in my desktop applications.
And I just solve it with careful reading in ht*ps://developers.facebook.com/docs/howtos/login/login-for-desktop/. The solution is to change redirect_uri from ht*p://www.facebook.com/... into ht*ps://www.facebook.com/...
Hope this will help you just like it help me
NB:
change ht*p into http
sorry i have to change the http into ht*p so that i can post the answer.
We have a Facebook app that publishes URLs to a user's newsfeed via the Facebook iOS SDK. These URLs are for pages that have OpenGraph attributes defined and we've verified in the Facebook Linter that it's correctly defined.
However, periodically we are seeing that Facebook won't correctly parse the OpenGraph attributes and have less than a stellar post to Facebook:
We will most often get posts parsed correctly resulting in posts like these:
We'll periodically get posts like these:
However, you can see this later post works correctly in the FB Url Linter: https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fchewsy.com%2Fr%2Fa%2F1bhLT.
However, sometimes the URL Linter will report a 503 but I see nothign in our logs. And even more odd, when the URL Linter reports the 503, it will shows that it can read the OpenGraph attributes defined. See this screenshot:
Since this is inconsistent, my first guess was this was a Facebook issue so I opened a bug. However, since I'm not seeing this issue rampant in the newsfeed with other apps, I'm starting to wonder if we aren't following the right steps to publishing FB content.
For example, are we supposed to post to the URL Linter first, then publish via the Graph API? This seems like a ridiculous extra step, but I'm grasping at straws here...
It's probably due to fact that in a time Facebook Linter visited your site it wasn't accessible, just couple of refreshes on a Linter Tool with URL you've provided resulted in Bad Response Code error, returning 503 status code:
http://chewsy.com/r/a/1bhLT"">
You should dig in logs of your application/site to discover the real reason why this happen and fix it.
Just a quick note that this should no longer be happening for CloudFlare users. We pushed a fix for the 503 debugger issue moments ago that appears to have fixed the problem. Please contact us if you see any other issues with the Facebook Debugger.