Thanks, Ellsass. A few more questions to better help us identify the issue: - You're sure you're using the same consumer key and secret for these requests and not switching between different API keys and possibly mis-matching access tokens with the wrong consumer key? - Have you been making any changes to your application record on twitter.com or dev.twitter.com before or during these requests?
Thanks! Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 18, 2010 at 3:27 PM, Ellsass <[email protected]> wrote: > Today (5/18) I haven't gotten the error at all. It was happening > occasionally on 5/16 and very often on 5/17 during the daytime and > evening, eastern US. > > My request, in PHP (I've modified EpiTwitter slightly to deal in XML > rather than JSON): > > $twitterObj = new EpiTwitter($consumer_key, $consumer_secret, > $_COOKIE['oauth_token'], $_COOKIE['oauth_token_secret']); > $twitterInfo = $twitterObj- > >get_statusesHome_timeline(array("count"=>"$numTweets")); > > > and then the contents of $twitterInfo->responseText is this: > > <?xml version="1.0" encoding="UTF-8"?> > <hash> > <request>/statuses/home_timeline.xml?count=100</request> > <error>Invalid application</error> > </hash> > > > > > On May 18, 9:55 am, Taylor Singletary <[email protected]> > wrote: > > This sounds strange. Can you share the return XML you get when it says > > "invalid application?" > > > > Taylor Singletary > > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Mon, May 17, 2010 at 3:56 PM, Ellsass <[email protected]> wrote: > > > When attempting to retrieve a timeline (or mentions, etc) I am getting > > > the response "Invalid application" in the XML. I am using Oauth (with > > > EpiTwitter). It just started today, and occasionally I will be able to > > > retrieve the timeline with no problems. I am not hitting my rate limit > > > (I am the only one using the app) and there are no messages on > > > dev.twitter.com. If I delete and re-register the app it will work a > > > few times, then die again, going back to working intermittently. > > > > > Any idea what could be causing this? I haven't changed any of my API- > > > calling code for a few days. >
