Twitter posting is broken

[Vimal]

Taplynx Team,

Twitter posts are giving error with this message: "<XML version - "1.0" ...error code="34"> Sorry, that pages does not exist...".

Most likely because of Twitter's new 1.1 API would be my guess. Could you please address it at the earliest?

Thanks,

Vimal

[rjcarter]

We are experiencing this problem as well.

[Mike@TapLynx]

Okay, after looking into this Twitter issue today we found a possible reason for this particular error. 

Look for this in the logs:

 Using TapLynx Twitter consumer key and secret. These won't work on the device -- make sure to register your app with Twitter, get your own consumer key and secret for your app, and request xAuth access. If you have any questions about this, please ask on the Google Group.

If that is present, you will need to follow the instructions given in the message. We were getting the same XML error without those set.

Please let us know if this fixes the issue or not. 

Thank you. 

- Mike

On Wednesday, October 17, 2012 11:47:54 AM UTC-6, Mike@TapLynx wrote:

Thank you for letting us know. We are looking into the situation right now. We will keep you posted with anything we find out. We appreciate your patience. 

-Mike

[Vimal Singh]

Mike,

Thanks for looking into this but your suggested change of having our own consumer key and secret was already implemented way back in May 2011.  See the Wiki link there:

http://wiki.taplynx.com/wiki/Twitter_OAuth_Change_Implementation

Twitter posts were working fine until recently.  That's why I was suspecting if Twitter's recent 1.1 API release (which many other applications have reportedly been affected as well) could be the cause.

Thanks,

Vimal

--
--
 
 

[Mike@TapLynx]

Vimal,

I'm going to speak to our engineer again and see what else it could be. 

Thank you for your continued patience. 

- Mike

[Vimal Singh]

Thanks Mike. 

Looks like in Twitter's 1.1 version, the new API dropped support for XML, Atom, and RSS with support for JSON only.  

What output formats will API v1.1 support?

API v1.1 will support JSON only. We’ve been hinting at this for some time now, first dropping XML support on the Streaming API and more recently on the trends API. XML, Atom, and RSS are infrequently used today, and we’ve chosen to throw our support behind the JSON format shared across the platform. Consequently, we’ve decided to discontinue support for these other formats. For historical context, when we originally built the API all major languages did not have performant, well vetted libraries supporting JSON - today they do.

Twitter version 1.1 FAQs:

https://dev.twitter.com/docs/faq#rest-api-v11

-Vimal

--
--
 
 

[Mike@TapLynx]

Vimal,

Thank you for the heads up. Our engineer is still working on the problem. I will post a solution as soon as possible. 

Thank you. 

- Mike

[Mike@TapLynx]

Update: Twitter's recent API changes have resulted in incompatibility issues. We have a fix in the works that should be posted soon. Apologies for the delay. As soon as it's available we will post here. 

Thank you. 

- Mike