I was able to get things to work again by using https for the affected timelines. The api docs do not state that https is required. Is this some issue with the twitter api? Also not all users seem to be affected.
Seems like another person was having a similar issue: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/b12eb886ec477465 On May 31, 2:30 am, John <[email protected]> wrote: > I have an app that hasn't changed and has been working fine for > months. But the other day it stopped working. Heres what i'm > experiencing: > > -login, favorites, lists still works fine > -home, mentions and DMs give 'invalid signature' oauth error > > Other people have reported the same issue but for others the app works > fine. > > This first occurred after I came back from vacation from another > country and I tried to use the app from a device that I hadn't used in > months. The date/time on this device was incorrect causing oauth to > not work. When I update the date/time it allowed me to login but was > getting errors for home/mentions/DMs. The error seemed to pass over to > my other device which never had this problem and had been using on > vacation. > > I tried testing my twitter account with other twitter apps on the same > device and had the same issue on one but worked fine on another. > > any ideas? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
