We are recieving a larger number of facebook conversations api access errors, even after checking the access token.
We need to check the User has MANAGE, CREATE_CONTENT, or MODERATE task on the Page
calling /
{uid}
/accounts?access_token=xxxx we get a list of Pages and tasks available.
One example of this:
Fsbwa Bank
```
{
"access_token": "xxxxyyyy",
"category": "Profile",
"category_list": [
{
"id": "2623",
"name": "Profile"
}
],
"name": "1st.security.bank",
"id": "102275655380928",
"tasks": [
"ANALYZE",
"ADVERTISE"
]
}
...
```
The access token analysis shows the proper scopes, but the User who requested them does not have the tasks needed for calling the conversations API.
I reccomend we do a few things.
1. On account refresh set a flag on the Page to indicate messaging/conversations available or not.
2. For pages that have scopes for conversations, but not tasks then send an email with instructions on how to do this. Also set the page to disable conversations API calls for the time being.
3. Enable front end to toggle messenger for Pages. When toggled on do the above checks, if they fail show some in app instructions on adding the appropriate tasks for the User.