Thanks for the reply,
Actually, my main problem is: sometimes getting 401 error for
authenticating users, but sometimes not getting the error, i use my
own twitter accounts to test it, and i'm sure that i didn't make any
changes to the accounts. I also readed through the discussion and
developer at google code, there are some people reporting the same
problem with what i'm experiencing on.
Do you know why this problem occured..?
On Jan 4, 11:27 am, Mark McBride <mmcbr...@twitter.com> wrote:
> Can you provide more details? Once you start getting401errors for a
> user, do you continue to get them? One explanation is that users have
> changed their twitter passwords since you stored credentials.
> On Sun, Jan 3, 2010 at 6:39 PM,dimas<dimas.priya...@gmail.com> wrote:
> > Does anybody has any ways to solve it??
> > Is it problem from Twitter API itself??
> > Thanks before.
> > On Dec 30 2009, 10:25 pm,dimas<dimas.priya...@gmail.com> wrote:
> >> My application authenticating user via web login, then save the needed
> >> credential and running API call in background task using cron.
> >> Sometimes the requests return a401unauthenticated error, and
> >> sometimes
> >> they don't> I readed on this
> >> issue:http://code.google.com/p/twitter-api/issues/detail?id=1052&can=1&q=%2...
> > .>
> >> and the last post says:
> >> "This was the result of an issue with an experimental service we were
> >> testing. The bug should be resolved."
> >> Is it the issue of experimental service testing??
> >> I'm not saving the log, but the error is around the "verify
> >> credentials" on
> >> the background task. And "get access token" on web login when
> >> redirecting
> >> back to my application.