We are using Facebook Login and public_profile advanced access for an iOS app. All reviews are done and on the dashboard there is nothing to submit for a review, all green lights(Business Review is done). When we try to login via an account which has a role on the meta developer "published"(live in old terminology) app, we are seeing the warning below.

Submit for Login Review Some of the permission below have not been approved for use by Facebook.

Submit for review now or learn more

If you are not using Limited Login, you will need to hand all Graph API calls using Graph API, IOS. The access token will not be valid. To learn more about changes to the Facebook SDK for iOS and how you can continue using the Facebook Login SDK, visit the blog.

Issue is that, when you click on Submit for a Review on the warning, it takes you to App Review tab on the meta developers dashboard which does not have anything to submit for a review and everything looks ok.

Anyone has ever seen this? How did you solve the issue? Thanks for the help!

We have doubled checked that app is only using login and public_profile. We are on the newest SDK due to Privacy Manifest requirements of the iOS that is why we are using Limited Login on iOS as well. Normally we should not see this warning but it keeps showing up. I could not find much at the internet regarding the note about "Graph API". Not sure if we somehow call Graph API still but since SDK is updated, this should not happened. How can we check this and make sure that we are not using Limited Login properly or still using Graph API somewhere?

We have an application with Facebook that has been successfully granted several permissions in the past. I know that the process of getting app permissions with meta has always been unnecessarily difficult and I expected nothing less when applying for the 'Page Public Content Access' permission.

However, this has turned out to be substantially more challenging than predicted.

Initially we tried accessing the permission from our currently 'live' application which didn't work and were quickly guided by meta support to create a test application (a copy of the parent application) and attempt to use the endpoints/permissions based on this 'development' application.

This is what we did and we added the 'pages_show_list' and 'pages_read_engagement' permissions before requesting an access token in order to test the 'pages/search' endpoint that we would be screencasting for our permissions approval.

This though is giving us the exact same results

{ "error": {     "message": "(#10) This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature or the 'Page Public Metadata Access' feature. Refer to https://developers.facebook.com/docs/apps/review/login-permissions#manage-pages, https://developers.facebook.com/docs/apps/review/feature#reference-PAGES_ACCESS and https://developers.facebook.com/docs/apps/review/feature#page-public-metadata-access for details.",     "type": "OAuthException",     "code": 10,     "fbtrace_id": "AICjKBRUbuIP8RrzxSfYG1C"   } } 

I feel like I've read the documentation a million times and it has not improved my understanding, nor my mood towards their application mechanism.

What are we doing wrong here?

I am trying to create an application where the application requires access to the Facebook posts(along with post title, posted date, author, all comments and replies). I was looking at the Permissions Reference for Meta Technologies APIs and I noticed a permission named user_posts that allows access to posts that user has made on their timeline. But I want access to any post(with all info like title, date, comments, etc.) that the user has access to. The user needs to copy and paste the url of the Facebook post to my application and I need to get access to the information on that post and work with it to give the desired output to the user.

Is this possible using Facebook OAuth? If not, is there any other way I can accomplish this?