Unable to Post to Twitter; Bad Image

Resolved elrebrin
(@elrebrin)

6 years, 6 months ago

Even before the 4.0.2 update (I actually updated to it hoping it would fix this) – we’ve been unable to push out Tweets since Saturday 10/14 for some reason.

Here’s an example of the error I receive:

[2017-10-18 08:15:14] [User ID:2] – [Error] [Twitter – #gaming] – -=ERROR=- Array ( [pgID] => [isPosted] => 0 [pDate] => 2017-10-18 12:15:04 [Error] => Resp: {“errors”:[{“code”:324,”message”:”Bad image”}]}| Error: | MSG: [Updated] Activision Granted Patent Related To Multiplayer Microtransactions – http://bit.ly/2hOBkcz | #gaming ) [Updated] Activision Granted Patent Related To Multiplayer Microtransactions

Anyone ever had this and resolved??

The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)

Djib's
(@djibs13)

6 years, 6 months ago
I have the same problem. Also with another plugin “Wp-Twitter pro”
- This reply was modified 6 years, 6 months ago by Djib's.
Plugin Author NextScripts
(@nextscripts)

6 years, 6 months ago

This error means your server is messing up with the size of the uploaded image file. Twitter does not like that anymore.

We will include a workaround fix in the next release.

Thread Starter elrebrin
(@elrebrin)

6 years, 6 months ago

@nextscripts – do you have an ETA on that? This is a huge issue.

Plugin Author NextScripts
(@nextscripts)

6 years, 6 months ago

Please update to the latest version 4.0.4. This problem has been fixed there.

Djib's
(@djibs13)

6 years, 6 months ago

This is not completely corrected.
The image is uploaded, but there are artefacts.

Example :

Facebook met en place le système d’abonnement payant pour les articles de certains médias ➡️ https://t.co/6ISGeU2eWd pic.twitter.com/JIFznfETT2

— KultureGeek.fr | Actu High-Tech et Geek📱💻🎮 (@KultureGeekFr) October 19, 2017

or

Amazon annonce l'arrivée de nouveaux Dash Buttons en France ➡️ https://t.co/pK58MT2YIH pic.twitter.com/NIuPJUk3h2

— KultureGeek.fr | Actu High-Tech et Geek📱💻🎮 (@KultureGeekFr) October 19, 2017

Thread Starter elrebrin
(@elrebrin)

6 years, 6 months ago

@nextscripts – works for 1 post, but there was a 6 minute delay and I did see 1 artifact similar to the other user.

Thread Starter elrebrin
(@elrebrin)

6 years, 6 months ago

@nextscripts – we just received “Bad Image” on a tweet again and it’s super slow to push out or even error out

Djib's
(@djibs13)

6 years, 6 months ago

we just received “Bad Image” on a tweet again and it’s super slow to push out or even error out

we also, some post have “bad image”

Thread Starter elrebrin
(@elrebrin)

6 years, 6 months ago

Now seeing artifacting on Images.

https://i.gyazo.com/225c1da4a5d49b86e80edf41159ebc72.png

Djib's
(@djibs13)

6 years, 6 months ago

@nextscripts ??

Plugin Author NextScripts
(@nextscripts)

6 years, 6 months ago

Well, your server is changing the uploaded files. Twitter used to tolerate that. It looks like it is not ok with that anymore (since the depreciation of the “update_with_media” endpoind). All altered images cause “bad image” error.
New enpoint allows base64 encoding for images, but it looks like encoded images are still getting alerted by your server, Instead of “bad image” error, encoding is causing artifacts.

What can be done?
Best solution will be to fix your server. You need to find a VERY good server admin who will be able to determine why your server is doing that and how to fix that.

We are still investigating the problem and trying to find out if anything can be done from our code.