Our app stores the twitter username and password in a database (switching to OAUTH soon) so it can then do specific scheduled task, such as taking an RSS feed and making them into Tweets, do specific searches, check for new followers, etc.. Also when you log into our app it shows you your home_timeline and has the ability to for your mentions. It takes the stored username and password and sends the information via CURL to the twitter API. So times they are authenticated and some times they are not.
Everything was working perfectly fine until a few weeks ago. On Dec 3, 3:41 pm, Peter Denton <petermden...@gmail.com> wrote: > Are you using other apps or alternate account credentials? i.e. have you > checked for a cookie conflict? > > On Thu, Dec 3, 2009 at 10:22 AM, jaybenoit <jayson.g.ben...@gmail.com>wrote: > > > I am experiencing an issue with our app, that uses Basic Auth, where > > periodically it can not authenticate the user when trying to perform > > any API calls for fucntions that require authentication. > > > My code has been working for several months and now this seemed to > > start happening mid to late November. > > > It is really weird because it works half the time and the then can not > > authenticate the other half. It is not a rate limitation as I have > > already checked that to make sure. Has anybody else had this issue > > occur? Is there some other type of limitation that I am not possibly > > aware of that would send back the "Could Not Authenticate you" error > > even when we are sending the correct login and password? > > > Any help would be appreciated.