Error when generating a Page Token

(Gosha Malanichev) #1

Getting this error when trying to generate a token for a page.

See screenshot.

Followed the usual process for both the app and page. What am I missing?

Thanks!
Georgy

(John Jackson) #2

I think you’re getting this because you haven’t yet had your app approved. You should be able to click OK and go ahead using the bot.

Once you’ve approved it, other users can use the bot and they won’t see that warning.

Hope that’s helpful, enjoy the product! :+1:

(Gosha Malanichev) #3

Thanks John, but if even if I click ok in that dialog, token doesn’t get generated…

(John Jackson) #4

Sorry you did say in your post it usually works.

I have come across this http://stackoverflow.com/questions/38909357/webhooks-failing-with-invalid-scopes-pages-messaging-subscriptions which suggests it may be a problem at FB.

There is an alternative way to get your token explained in that link too.

Would you be able to try that?

(Gosha Malanichev) #5

Cool, thanks. I’ve been able to generate a token via Graph API as per the SO post, but now stuck with the “Setup of Facebook Messenger integration failed. Please check your Application ID, secret and Page Access Token. Details: (#230) permission pages_messaging is required to register webhook for messages or deliveries” error, seems similar to New Messenger bot - Error

(Horia Velicu) #6

You have to have in both drop down lists the name of the page, not just in the bottom one and stay with open graph up. It will generate a code and get you further with no error, but I still have an issue of the bot not responding.

Just another user

(Gosha Malanichev) #7

The top dropdown is for the app, though? Second one for the page. Still no luck. Must be something at FB’s end.

(John Jackson) #8

It does seem likely this is a FB issue, there is now a bug report: https://developers.facebook.com/bugs/281723762198561/

(Gosha Malanichev) #9

Nice. Hopefully it gets resolved soon!

(John Jackson) #10

The bug has been accepted and assigned by FB, and they offer a workaround:

Thanks for reporting the issue. We have a fix ready and we’re rolling it out to production at the moment. As a workaround you should be able to use the beta tier in the mean time: https://developers.beta.facebook.com/apps/89000000000000/messenger/ All the best, David