I call the POST api for {comment_id}/likes. The response I receive is an Error (#200) I check using the GET api for {comment_id}?fields=can_like, he field can_like is set to true.

I'd like to bring to your attention an issue we've observed regarding the deletion of comments on Facebook Pages. As of January 22, 2024, at 01:26 (UTC), it appears that the comment delete endpoint no longer returns success=true upon successful deletion, as indicated in the documentation.
Instead of the expected response:
{
"success": true
}
We are now receiving an empty response:
[]
This inconsistency has been noticed since the specified date and time. The documentation, found at https://developers.facebook.com/docs/graph-api/reference/v18.0/comment#deleting, clearly states that the expected response should include "success": true.
To illustrate the issue, you can refer to the post link: https://www.facebook.com/feelgameworld/videos/1365948704273842/ and the comment link: https://facebook.com/701647665327134_2341614089562131.
We would appreciate it if community members could confirm whether they are experiencing the same behavior or if this is an isolated incident. Your insights and feedback on this matter are invaluable.
Thank you for your attention and assistance.

Hello community,
Currently, my application uses an authentication endpoint that directly passes user credentials to obtain a token. However, I am aware that this approach is not secure, and I am considering migrating to OAuth.
I would like to understand how I can implement OAuth in this specific endpoint while ensuring compatibility with tokens already generated by the application.
The current endpoint looks like this:
import requests
url = "https://b-graph.facebook.com/auth/login"
headers = { 'x-fb-connection-quality': 'EXCELLENT', 'x-fb-connection-type': 'WIFI', 'user-agent': 'Dalvik/2.1.0 (Linux; U; Android 12; Pixel 3 Build/SP1A.210812.016.C2) [FBAN/Orca-Android;FBAV/412.0.0.15.69;FBPN/com.facebook.orca;FBLC/en_US;FBBV/481775700;FBCR/Verizon;FBMF/Google;FBBD/google;FBDV/Pixel 3;FBSV/12;FBCA/arm64-v8a:null;FBDM/{density=2.75,width=1080,height=2028};FBBK/1;FBLR/0;FB_FW/1;]', 'x-tigon-is-retry': 'False', 'x-fb-http-engine': 'Liger', 'x-fb-client-ip': 'True', 'x-fb-server-cluster': 'True', 'x-fb-device-group': '7991', 'x-fb-sim-hni': '311390', 'x-fb-net-hni': '311390', 'x-fb-request-analytics-tags': 'unknown', 'authorization': 'OAuth null', 'content-type': 'application/x-www-form-urlencoded', 'x-fb-friendly-name': 'authenticate', }
data = { 'access_token': '256002347743983|374e60f8b9bb6b8cbb3.........', 'adid': '2c4afb4e174A84Ea', 'api_key': '25600.........', 'client_country_code': 'US', 'community_id': '', 'cpl': 'true', 'credentials_type': 'password', 'currently_logged_in_userid': '0', 'device_id': '9047e4fc-eceb-438b-8f67-aa694fafbb20', 'email': [...]', 'enroll_misauth': 'false', 'fb_api_caller_class': 'AuthOperations$PasswordAuthOperation', 'fb_api_req_friendly_name': 'authenticate', 'format': 'json', 'generate_analytics_claim': '1', 'generate_machine_id': '1', 'generate_session_cookies': '1', 'jazoest': '22621', 'locale': 'en_US', 'meta_inf_fbmeta': 'NO_FILE', 'password': '#PWD_MSGR:1:1705810723:AYOghZx3lG7MDND1yGEAAXCX3pkimdUSGPOGcnKDF+MUs9uB3rGuWQVyRCT1d44GIQMbqfhs71COieDt16JTy5zincTh5tVRvV4uTA3CIH1UNyHUtM8K3W8lZCcQEUZstsgx/YNlHjY4pcOs9b/xsjsF7OxGAr2mnCVtGinbXYxFjPHJcar9yFMhQ4ClKo74qJdGu4o0ZO4eRfMyjI4uHlgPWjzHMlntmP98jtIYKA5OW2fVCHFjrYsmv+scYS174lMvHaqOkM1ep2qqYW3NeTLM6OUZTvVap4maP6Q8xB4Z8mB7bh+rWmnD..........aQd68KC9nnjl1t3zTDEdw9qpq39cLOITnXRnnGWGcgMISvpqMWxb6ywFF30U4J5lbKYcmtqAr02OSw==', 'secure_family_device_id': '', 'sig': '30dd2df36ed4eb23397f9ea695f.....b', 'source': 'login', 'try_num': '1', }
response = requests.post(url, headers=headers, data=data)
print("Response Status Code:", response.status_code) print("Response Text:", response.text)
My intention is to transition to a more secure approach using OAuth while ensuring that the application continues to work with the same token that this route generates.
Any suggestions or guidance on how I can efficiently and securely make this transition would be greatly appreciated. Thank you in advance!

We are receiving following error: (#10) To use 'Oembed Read', your use of this endpoint must be reviewed and approved by Facebook. To submit this 'Oembed Read' feature for review please read our documentation on reviewable features: https://developers.facebook.com/docs/apps/review.
our app has received advanced access to Oembed Read a few months ago already and has worked for the past months, now all of a sudden we need another review to get access? Is there another issue that's causing this or is this a facebook issue?

As a heads up, we've seen that since 2024-01-18 20:26 (UTC) the comment delete endpoint returns
[]
isntead of
{
"success": true
}
when successfully deleting comments.
The docs are clear that it is supposed to be the latter https://developers.facebook.com/docs/graph-api/reference/v18.0/comment#deleting
Can anyone confirm this?
Workaround is to just not check the result diligently.