Sudden Error (Code: 100, Subcode: 2018047) When Sending Images via Messenger API
Hi everyone,
Since 19:20 Bangkok time today, I've been encountering an issue when trying to send images via the Messenger API. I'm receiving the following error:
'code': 100,
'error_subcode': 2018047
This error occurs when I attempt to send an image using an S3 URL that has worked without issues for a long time. Here's an example of the API request body I'm using (with sensitive data hidden):
{
"message": {
"attachment": {
"payload": {
"url": "https://
},
"type": "image"
}
},
"messaging_type": "MESSAGE_TAG",
"recipient": {
"id": "
},
"tag": "CUSTOMER_FEEDBACK"
}
This has been working fine until today, and I'm not sure what's causing the sudden issue. Has anyone else experienced this or knows what might be going on? Any insights or advice would be greatly appreciated.
Thank you!
Hi - we are encountering the same issue and impacting Production. Can someone take a look at this asap?
Having the same error, created a post here: https://developers.facebook.com/support/bugs/1580262999501820/
It seems to not work with any image link I've tried aside from images served by Meta CDN (e.g. the images you see on facebook.com).
Having the same error, created a post here: https://developers.facebook.com/support/bugs/1580262999501820/
It seems to not work with any image link I've tried aside from images served by Meta CDN (e.g. the images you see on facebook.com).
Having the same error, created a post here: https://developers.facebook.com/support/bugs/1580262999501820/
It seems to not work with any image link I've tried aside from images served by Meta CDN (e.g. the images you see on facebook.com).
Having the same error, created a post here: https://developers.facebook.com/support/bugs/1580262999501820/
It seems to not work with any image link I've tried aside from images served by Meta CDN (e.g. the images you see on facebook.com).
For everyone else in the Thread, we solved by using a Cloudfront distribution in front of our S3 bucket (which contained our domain name: static.callbell.eu).
Using the CF distribution solved the problem.
We are having the same exact issue.
We are having the same exact issue.
It still exists
We have been having the same issue. On sending images returns us the error [...]. It's happening consistently.