How should I handle 401's not authorized when sending via oauth and
its twitter hiccuping and not an actual NOT Authorized? The reason I
know its not a true 401 is because the updates appear on the twitter
profile, and then 30min or so later I receive the mobile
notification.. When looking at my
It was my fault. :-) They key was coming back null, needed to update
my db.
thanks,
-k
On Oct 8, 11:57 am, kthom kapen...@gmail.com wrote:
How should I handle 401's not authorized when sending via oauth and
its twitter hiccuping and not an actual NOT Authorized? The reason I
know its
