We’ve had a bunch of customers experience this for a while over the years. Just ran into another case with this 1.5 MB, large JPG:
Previous related threads:
https://twittercommunity.com/t/feedback-for-upcoming-changes-to-png-image-support
We’ve implemented some internal resize logic on fail but this would be an awesome one to see fixed that I have to assume is affecting a lot of API users (and their customers).
system
Closed
#2
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.