Unable to read post data with error #10 use page public content access permission from api
Anyone face the following issue?
Not able to get post information using ${pageid}_${postid} format even we already have all the permission required "pages_read_engagement", "pages_read_user_content".
This was working yesterday and it's no longer working now.
https://developers.facebook.com/support/bugs/962503249211913/
same here
same here too
We try to remove page id. It working for me
meta has fixed the issue yesterday 7pm GMT+8. https://metastatus.com/graph-api
meta has fixed the issue yesterday 7pm GMT+8. https://metastatus.com/graph-api
I apologize for the confusion this may have caused. It looks like you're having trouble fetching post information using the ${pageid}_${postid} format. This problem seems to be common lately. Here are some things you can try: 1. Check your app review status: Make sure your app has passed the app review process. Some permissions and features, such as access to public page content, require successful completion of the app review process before your app can access live data. 2. Business Verification: This permission or feature is only available with Business Verification. You may also need to sign additional contracts before your application can access the data. 3. Check Admin Roles: While you're testing your app and before you submit it for review, your app can only access content on a page where it's true: The person who holds the Admin role for the page also holds the Admin, Developer, or Tester role on the app. If these steps do not solve your issue, I recommend contacting the Meta developer community or Meta Support for specific assistance. I wish you luck, and let me know
I apologize for the confusion this may have caused. It looks like you're having trouble fetching post information using the ${pageid}_${postid} format. This problem seems to be common lately. Here are some things you can try: 1. Check your app review status: Make sure your app has passed the app review process. Some permissions and features, such as access to public page content, require successful completion of the app review process before your app can access live data. 2. Business Verification: This permission or feature is only available with Business Verification. You may also need to sign additional contracts before your application can access the data. 3. Check Admin Roles: While you're testing your app and before you submit it for review, your app can only access content on a page where it's true: The person who holds the Admin role for the page also holds the Admin, Developer, or Tester role on the app. If these steps do not solve your issue, I recommend contacting the Meta developer community or Meta Support for specific assistance. I wish you luck, and let me know
The 'Oculus QFB MDM' app that appears unexpectedly appears to be part of Mobile Device Management (MDM) for Meta Quest for Business. MDM is the third application and website use of Oculus-designed hardware technology. You can install MDM for your longest devices through Device Manager¹[1]. If you are seeing this app and did not install it yourself, there may be a system error or it may be part of an update or setting change by management. Here are some steps I did: 1. Check MDM Settings: Make sure the MDM settings are correct in Device Manager and you have not installed the app head-on. 2. Reboot the device: Periodically, rebooting the device may solve temporary problems that occurred due to the blocking being stuck. 3. Contact Technical Support: If you have a problem, it is preferable to contact Meta Quest for Business Technical Support for professional assistance. 4. Check for updates: Ensure that all new updates for the device have been installed, as some new updates may be updated. For information on how to use MDM with Oculus for Business, read
The issue seems to have resolved itself.
I doubt we're going to get an explanation though.
We have the same problem with more than 30K users
it seem like issue is resolved
Same here
Same here
Same here
same here
This error started happening 4-24, approximately at 5pm PST.
same here
Same here too
same here too
We're also experiencing this.
we found api feed and post . if we ignore the parameter attachments . it working for me
we found api feed and post . if we ignore the parameter attachments . it working for me
Same here
same here
same here