Facebook Messenger App Invalid Scope - permission: pages_messaging_subscriptions - facebook-apps

I'm attempting to connect a Facebook Messenger App to one of my pages..
I've connected Facebook Messenger Apps to pages before.
But this is the first time I've received this error...
What gives?

This is a bug and we are currently working on it. In the meantime, please use our beta tier or generate the page access token through our API. To use the beta tier, you can access the following:
https://developers.beta.facebook.com/apps/89000000000000/messenger/

we got same error and here is helpful answer
https://developers.facebook.com/bugs/281723762198561/

In my case, my app was live which was preventing access token generation.
Just go to app dashboard and disable the live checkbox as below:

Related

Can't get my app reviewed in Facebook API

I can't get my app to be reviewed through the Facebook API.
The app is purely a facebook messenger bot, and the app type is "business".
I have configured the specific permissions I need, however I recieve an error that states "You do not have any platforms eligible for review. Please configure a platform on your Settings page."
I also cannot add my app domain in the basic settings, as whenever I press save changes, the url does not save and disappears.
Additionally there is no option to make my app live.
Any advice?
The error message
I am leaving this answer in the event someone else needs it. It was an answer suggested by Facebook support when I encountered the same problem.
Go into App Settings and add a platform "Website"
Just add your website URL.
If the requested permission is just Messenger based then the website will not be accessed or tested.

Botframework v4 - Facebook Channel - Operation returned an invalid status code 'Forbidden`

Last year I developed a chatbot with Microsoft Bot Framework that I integrated in the Facebook Messenger of a page. Everything worked fine until 16th of December (last successful log). The page is not used by a lot of people therefore the application might have worked also longer than that.
Today I tried to use the chatbot again and I did not get any response. In the Logs I just found the error message "Operation returned an invalid status code 'Forbidden`".
After a bit of Debugging I found out that the problem is sending messages back to the Facebook Messenger.
context.SendActivityAsync(...)
I did not change any configuration within my Azure Bot Channel registration recently. I am aware of the privacy changes within the Facebook API, but as I already struggle with sending a simple text response like "Hi" I assume that cannot be the problem. Also the permission scheme has changed for Facebook apps. I have the permission for "pages_messaging". Do I need another permission now? Or did I miss another change in the Facebook API?
Technical Details:
Facebook API Version v6 (tried also v9 but no change in behavior)
Chatbot based on .Net Core 2.1
Bot Builder SDK v 4.11
Any hints what I did wrong or where I can look for further information is much appreciated.
Edit: I tried to add a new page to my Facebook App and get following message:
There is a hint that a permission is missing, but I cannot find out which one I require. As I only send responses to FAQ's and if required handover to the customer service inbox I just requested the "pages_messaging" permission. Do I require any other permission now?
I found the problem. For everyone that might have the same problem:
In our case the administrator that added the Facebook pages to the application was removed from the admin permission list of the pages. After re-adding the admin permissions for the pages the bot started working again.

API Exception (OAuthException: Cannot call API on behalf of this user)

Got the following exception when calling api (/me) using the latest PHP SDK.
OAuthException: Cannot call API on behalf of this user.
The same exception appears for some facebook account only. Any clue?
I found the source of the problem (on our site, at least). In Facebook's developer console (https://developers.facebook.com/apps), our app was showing an invalid privacy policy. Due to this, Facebook had automatically placed our app into Sandbox Mode.
Updating our privacy policy and (more notably) removing our app from Sandbox Mode caused this error to cease.
Other users seem to have had some success with removing regional (country-specific) restrictions on who can and cannot log in to their app (https://groups.google.com/forum/#!topic/django-social-auth/XaE5dFXEqhA)
Additionally, #Igy's questions sound reasonable and might lead to finding a solution as well.
Best of luck! :)
Is that user's access token still valid? Has the user blocked you? Can you navigate to the user's profile manually? (i.e their profile might be unavailable)

Access ograph insights from another app without admin?

Been trying to get insights data from a page in another app (without admin), yet no luck.
Been using Facebook API to access 'insights' through Open Graph. I have two Facebook profiles:
one being the app holder
the other being some Facebook page not
related to the app.
I am able to get the data when the 'app holder' has admin rights on the 'Facebook page'.
I saw Odata app and tried that, yet I wanted to keep it within the Facebook app control.
I have also linked the application with the page, hoping that will work (yet no joy).
Am I missing some 'Facebook App setting' that I can use or is this not possible?
Any thoughts much appreciated.
Read the instructions on this page, it explains how to do it: obtaining a permanent facebook oauth access token

Facebook iphone connection

I have the next problem with the connection:
I can't connect to one app in facebook, but when I create a new app in facebook and I change the API and secret all is going good.
The problem is that I need to connect to the first one app in facebook, the other was only to test the connection.
What could be the solution?
Thanks
Without any additional information, no one is going to be able to diagnose this with any sort of certainty.
I would suggest checking to make sure that you've set the Facebook app to be classified as a "Desktop app" rather than a web app. If it's not set as a desktop app, Facebook will refuse the connection.
If that doesn't help, you need to provide some more details about the configuration of your app on Facebook and about what exactly you are doing to test the connection.