Sudden Error (Code: 100, Subcode: 2018047) When Sending Images via Messenger API
5

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://<xxx>.s3.ap-southeast-1.amazonaws.com/<xxx>.jpeg"
            },
            "type": "image"
        }
    },
    "messaging_type": "MESSAGE_TAG",
    "recipient": {
        "id": "<xxx>"
    },
    "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!

Billy
Gefragt vor etwa 4 Monaten
Wu

Hi - we are encountering the same issue and impacting Production. Can someone take a look at this asap?

30. August um 07:49
Ausgewählte Antwort
1

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).

30. August um 09:40
Gianluca
Ba

It still works with a few image links, you can try https://cdnphoto.dantri.com.vn/eL-ZcrtTv1j1DSa3dNnWcpMx-Pc=/zoom/378_252/2024/08/30/00036ee6jd-scaled-1725019551768.jpg

30. August um 09:45
Gianluca

Yep, I confirm it works. I also tried to create a new S3 bucket in us-west-1 and send the URL image without CDN and it seemed to work

30. August um 09:52
1

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.

30. August um 11:20
Gianluca
3

We are having the same exact issue.

30. August um 08:42
Testeur
Testeur

Was working up until yesterday morning too, just not working as of today for us.

30. August um 08:42
3

It still exists

3. September um 02:08
Px Px
5

We have been having the same issue. On sending images returns us the error [...]. It's happening consistently.

30. August um 08:18
Francisco