Getting error "User does not have social account for Twitter" when doing an image upload

[kapso]

When invoking this v1.1 end-point (https://dev.twitter.com/docs/api/1.1/post/statuses/update_with_media), we are getting the following error:

{“errors”=>[{“message”=>“Sorry, that page does not exist”, “code”=>34}]}

Anyone know whats going on here?

Please note that “/statuses/update.json” works fine, its only when we do a image upload when it fails.

Also note this same payload works with v1 (https://dev.twitter.com/docs/api/1/post/statuses/update_with_media)

Here’s the raw request we are sending out -

2013-04-09T19:35:23.189961+00:00 app[web.1]: --51646d7b
2013-04-09T19:35:23.189961+00:00 app[web.1]: Content-Disposition: form-data; name="status"
2013-04-09T19:35:23.189961+00:00 app[web.1]:
2013-04-09T19:35:23.189961+00:00 app[web.1]: "@cnn: @espn be careful. I was hit with quite a bill."
2013-04-09T19:35:23.189961+00:00 app[web.1]: --51646d7b
2013-04-09T19:35:23.189961+00:00 app[web.1]: Content-Disposition: form-data; name="in_reply_to_status_id"
2013-04-09T19:35:23.189961+00:00 app[web.1]:
2013-04-09T19:35:23.189961+00:00 app[web.1]: 321304692674134016
2013-04-09T19:35:23.190262+00:00 app[web.1]: --51646d7b
2013-04-09T19:35:23.190262+00:00 app[web.1]: Content-Disposition: form-data; name="lat"
2013-04-09T19:35:23.192142+00:00 app[web.1]:
2013-04-09T19:35:23.192142+00:00 app[web.1]: 37.486298
2013-04-09T19:35:23.192142+00:00 app[web.1]: --51646d7b
2013-04-09T19:35:23.192142+00:00 app[web.1]: Content-Disposition: form-data; name="long"
2013-04-09T19:35:23.192142+00:00 app[web.1]:
2013-04-09T19:35:23.192142+00:00 app[web.1]: -122.22992
2013-04-09T19:35:23.192142+00:00 app[web.1]: --51646d7b
2013-04-09T19:35:23.192142+00:00 app[web.1]: Content-Disposition: form-data; name=“media[]”; filename="RackMultipart20130409-8-1s5bew6"
2013-04-09T19:35:23.192142+00:00 app[web.1]: Content-Type: application/octet-stream
2013-04-09T19:35:23.192142+00:00 app[web.1]:
2013-04-09T19:35:23.192415+00:00 app[web.1]: �PNG
2013-04-09T19:35:23.192415+00:00 app[web.1]:
2013-04-09T19:35:23.192415+00:00 app[web.1]:
2013-04-09T19:35:23.192415+00:00 app[web.1]: �p�Z���)3�
2013-04-09T19:35:23.192415+00:00 app[web.1]: �R
2013-04-09T19:35:23.192415+00:00 app[web.1]: "��k��������$N�’�q�X|~D�F���S�#S�bҋ�2J�ҋ�S

[episod]

I’ve never seen this error before. Are you using any kind of library or framework that may be presenting you this error rather than it coming from the API to you directly?

[kapso]

You are right I have updated the error message we are getting from Twitter API

{“errors”=>[{“message”=>“Sorry, that page does not exist”, “code”=>34}]}

[episod]

Can you verify that you’re trying to reach https://api.twitter.com/1.1/statuses/update_with_media.json (as opposed to upload.twitter.com being the host)?

[kapso]

Actually we are using “https://upload.twitter.com” in this case. Is that the problem?

[kapso]

Ah I see this:

Important: In API v1.1, you now use api.twitter.com as the domain instead of upload.twitter.com. We strongly recommend using SSL with this method.