7

The messenger Send API gives me back the response (#546) The type of file you're trying to attach isn't allowed. Please try again with a different format. error code: 546, error_subcode: 154502

However, if I host the same exact image on Google Cloud instead of Amazon S3, then the image sends fine.

My link to the AWS image: https://s3.amazonaws.com/paloma-staging-public/files/conversation-step-56-80925.gif

My link to the google cloud image: https://storage.googleapis.com/callparty/thumbsup.gif

are there any special reasons that a link to an image stored on S3 would not work as an image attachment, but a link to an image stored on google cloud would work?

maxfowler
  • 1,168
  • 13
  • 23
  • 1
    When I click the AWS link my browser downloads the image. When I click the Google link it opens in the browser. So there must be some difference – WizKid Sep 25 '17 at 18:20

1 Answers1

5

The answer was that for the AWS link the ContentType of the file was not set.

While uploading to S3 I had to manually set the ContentType of the file appropriately ("image/gif", "image/png" etc.) and for the google cloud storage this must have been automatically set.

This is why the S3 link causes an auto-download, and the google cloud link displays the image in the browser.

maxfowler
  • 1,168
  • 13
  • 23
  • there must be also another reason why Facebook Messenger won't serve the images. I have the ContentType set on S3 but still Facebook Messenger (on mobile) won't serve the images in structured messages. However, on the desktop browser version it works fine. – robjeiter Dec 11 '17 at 14:53