Facebook feeds no longer work without Page Public Content Access

Yes , Page Public Content Access is required for using facebook feed but how can we show screencast if facebook feed is not working at all I am also stuck this problem. Here is the screenshot of error I am getting

Facebook's developer documentation states:

While you are testing your app and before you submit it for review, your app can access content only on a Page for which the following is true: The person who holds the admin role for the Page also holds a role in the app as app admin, developer, or tester. If you want the app to be able to access public content on other Pages, you must submit this feature for review. After the app goes to live mode, the app will not be able to see any Page public content without this feature.

However, I've been unable to access content for a page and app which meet the guidelines listed above.

A facebook bug was reported here, though it seems it may have been closed prematurely: https://developers.facebook.com/support/bugs/573130356406496/

Edit:
This bug report may be more relevant, and is still open:
https://developers.facebook.com/support/bugs/2139350026277360/?disable_r...

This seems to be an issue with Facebook & not with this module, hence closing this issue. For more info, kindly refer: https://developers.facebook.com/docs/apps/review/feature#reference-PAGES...

Still not possible to get this module working.

How or when are the facebook post fetched? On cron run? Why is there no documentation?????????
Which facebook permissions are needed?
manage_pages?
Page Public Content Access?

Could you solve the problem?

I fear that the new facebook policy require the approval of any app for manage_pages...
This is bad but not related to the module.
Anyway I'm still confused and can't understand if the "Page access tokens" is required to show the feeds, and if so, if the module need a patch or it can simply calculate the token using app ID + secret key

:/

How can we find out which permission we really need to read/import the posts of the own facebook page?

You think manage_pages is the right permission? I tried to get it in my review process, but FB denied it (maybe the screencast was not perfect, but I can not create a good screencast if there is NO way to test the application (Drupal module) using a testuser or in similar way. I could not find any way to test it and make a good screencast).

How can we find out the right way and solve it?

Well, I think that facebook doesn't mean that we need an approval for public content (except if they want force us to use their ugly stream plugin).

Maybe we are following a wrong path... we probably have to look into the "access token" thing. working on the explorer tool I can get the JSON feeds from my page submitting the lines:
GET / v3.2/MY_FACEBOOK_PAGE-ID/published_posts

no approval required.

We need a developer helping us to understand if the module needs a patch: if we need a new field "access token" in FB settings, or something like that.

This patch solved the issue for me. It adds a new facebook "User access token" field in facebook web service settings.

I think this issue can be closed and marked as duplicate. Documentation should be updated with two lines about User access token: you can get the token browsing https://developers.facebook.com/tools/explorer/ selecting your app and clicking on "Receive User access token".

Thank you very much!

I installed the patch (without problems) and added a Default Facebook User Token at /admin/config/socialfeed/facebook.

And now I am testing the module, but nothing happens.
There is no error message anymore.

I placed the Facebook Block on in my content region. The block is there but no facebook posts appear.

I run cron a lot of times on /admin/reports/status . But nothing happens.

How often are the FB posts fetched?
How can I start the fetching manually?
How can I see if the posts are beeing fetched or not?

Please have a look a the latest comments on https://www.drupal.org/project/socialfeed/issues/3018651 .

This issue is now fixed, kindly update the module.