I'm getting the same thing I was getting earlier: 401 Unauthorized
On Jul 9, 10:16 pm, Arnaud Meunier <arnaud.meun...@twitoaster.com> wrote: > On my side, things are back to normal since Matt announcement. > > On the previous bug, the error message attached in the body was "Could > not authenticate you." Are you receiving the same error message? > > Arnaud. > > On Jul 10, 1:34 am, johann <romef...@gmail.com> wrote: > > > > > Hi, > > > Same here, we re getting 401 on every OAuth requests. > > > thanks, > > > johann > > > @romefort > > CTO @ Seesmic > > > On Jul 9, 4:29 pm, Duane Roelands <duane.roela...@gmail.com> wrote: > > > > Yes, my application - which was working this morning - is now getting > > > 401s on every OAuth request. > > > > Something changed. > > > > On Jul 9, 7:25 pm, "dean.j.robinson" <dean.j.robin...@gmail.com> > > > wrote: > > > > > Everyone just magically got logged out of my hahlo4 beta, which was > > > > working fine an hour ago, and now when they reauthorize its not > > > > sticking. > > > > > OAuth login works fine, redirect back to hahlo4, but all api calls are > > > > returning 401 status codes. > > > > > Saw mention in another topic regarding whether twitter.com > > > > orwww.twitter.com > > > > should be used when making api call, all my calls are currently > > > > usinghttps://twitter.com > > > > > Anyone else experiencing anything similar?