Facebook Messanger App callback doesn't call my app - facebook

I created chatbot for Facebook. I tested in on one fanpage, got business and api permissions verfications from Facebook and I wanted to add the bot to more fanpages. I did it as before, I setted all Webhooks like messages, message_echoes but Facebook doesn't call my app. I'm checking it in debuging tool that shows network traffic to my server.
I tried to remove and add callback, fanpages, but nothing gets change.
The first fanpage still works all fine, but others don't call my bot on any message. Why?

assume you link your app to first fanpage with oauth dialog like this before.
oauth dialog : (See: https://developers.facebook.com/docs/marketing-api/overview/authorization)
https://www.facebook.com/v12.0/dialog/oauth
?client_id=<YOUR_APP_ID>
&redirect_uri=<YOUR_URL>
&scope=pages_messaging
when linking another fanpage with oauth dialog,
should click that edit settings button:
choose another fanpage:
now you receive webhooks from other fanpages.

So, problem was in my code. I was checking if request was sent using Symfony profiler. The problem was, it didn't save request if the process was stopped. And it was. I had "die" in some trycatch...

Related

Facebook app submission keeps getting rejected

I have made website where people can logon to with Facebook.
Ik keep getting this message every time I submit my request.
Your app's Facebook Login button does not work. Please make sure the
provided test user can successfully and consistently log in with the
Facebook Login button. See more about authentication.
Even though my created test user can login with IE, FF and Chrome.
Can anybody help me?
I am getting the same thing. I think you need to put the facebook javascript code in your website for them to see. I think that it is a bot reviewing your app, not a person, and it does not see it.

Webpage is not Available - Facebook Login Integration

I want to integrate facebook api to help in the registration process in my website. It was working fine before - the standard fb login button appears, the pop-up window to login to fb was working, some of the user data are obtained. However after several trials with me modifying the code as the feature isnt fully integrated yet in my site, whenever I press the login button what replaces the fb login page is "This webpage is not available." I already retracted the modifications I made to the point that it was back to the version wherein it was working before. I also created another app and replaced the app id and secret key, still it displays the same message. I do not know what is wrong. Please help.
Update:
I uploaded the project files to another hosting site and it works! Could it be that the previous domain is now blocked?
Please read the other posts, dude... we're all waiting for the FB to fix the issue...

apprequest fails to show up on user page

I able to post apprequest with my app server-side (app generated) without error. Returns Id and user to. I used FQL tool to query using appid and userid and I get results. But when I go to my facebook page I don't have a notification nor do I see app on the left side with count. Can this be a setup issue (my first FB app)? I have the app in sandbox mode, does that have anything to do with it?
how your app integrates with Facebook setting has both Mobile Web and Canvas checked. This will be primarily a Mobile Web app.
I'm able to create posts and those show up.
Any help will be greatly appreciated.
Thank you,
Rick
Indeed the issue here is sandbox mode.
Unless the user being sent the request is listed in the "roles" section of the application, the request won't really be sent out. The requests point back to your canvas URL, but with your application in sandbox mode, no one other than the team developing the application is able to reach that URL. Facebook doesn't display the notification because it wouldn't lead anywhere.
As far as you are concerned, the moment you get a request_id back after sending the request - it was completed successfully.

ui.methods permissions.request in share url

Earlier today I noticed a friend shared a Viddy video which made me curious. When I clicked on the share link I immediately got an authorization request dialog with custom text on the "next/login" button (Watch the movie). The URL for this share which triggered the behavior was this:
http://www.facebook.com/
connect/
uiserver.php?
app_id=125119214225766
method=permissions.request
redirect_uri=http%3A%2F%2Fwww.viddy.com%2Fvideo%2F2f44f934-bc2f-419f-b462-c46f261744ee
response_type=code
display=async
perms=email%2Cpublish_actions
auth_referral=1
fb_private_mode_enc=ASJbi0_rc8L9GhOWGzXF1eZQgqGW6WhIquDadvKiRi8uZRozkFn937vhtfsR_Krg8iM
I've looked around trying to find this feature documented. How am I suppose to generate such share URLs? I found some documentation on fbdevwiki.com, but that does not cover most of the arguments. If anyone could guide me to some documents I'd be very grateful.
That's an app using Authenticated Referrals so that users are prompted to grant permission directly on Facebook's chrome instead of landing on your app unauthenticated, and then bounced to an auth dialog and back to the app again.
The 'watch video' text in the auth dialog is because this app is publishing 'watch' actions in the Open Graph API
{edit} it appears the 'watch video' link is only shown for preselected partners and isn't available for all video apps
{/edit}
The generated url you see is generated by the app, you can achieve this by creating your own app and giving it the permission.
You can start by going to Facebook Developer

Problem with Old Facebook JavaScript SDK

I have an issue with the old sdk. Whenever I try to authorize a new user I get redirected to the home page of my app in the iframe. However, after I close the iframe and refresh the page, I can easily authorize a user.
But whenever I delete the application from my facebook account and try to authorize it, I'm back to the previous problem.
I've noticed the same bug in the different web applications. Hootsuite could be a good example.
Did facebook change the old api or did they change the authorization proces lately ?
I have a bug report open with Facebook for this. Go add your comment and vote it up.
http://bugs.developers.facebook.net/show_bug.cgi?id=12260