Your questions helped me find the issue. I'm using oauth-php and
apparently what I'm doing isn't properly setting the callback URL.
I'll look for the oauth_callback_confirmed flag for my error checking.

Thanks for the help!

On Sep 6, 4:11 pm, Taylor Singletary <taylorsinglet...@twitter.com>
wrote:
> Can you share as much information about your request token step as
> possible? This is the only step you should ever provide a callback URL
> in.
>
> Can you verify that you are usinghttp://api.twitter.com/oauth/*for
> all paths in this sequence.
> What is the value of oauth_callback on your request token step? Is
> this the only step that you are you providing this data? Are you
> presenting this via a query string parameter, an authorization header,
> a POST body, or any intermingling of the three?
>
> When you receive your response to request_token, do you get a
> parameter that indicates oauth_callback_confirmed=true?
>
> Thanks,
> Taylor
>
>
>
> On Mon, Sep 6, 2010 at 2:49 PM, G <glenn.wa...@gmail.com> wrote:
> > I will admit I'm not experienced with oauth at all and maybe I'm
> > sending bad data in the initial step. I fail to see why I would get an
> > appropriate request_token if that were the case though.
>
> > On Sep 6, 3:42 pm, Tom van der Woerdt <i...@tvdw.eu> wrote:
> >> Strange, you aren't the first one who reported this. I really think that
> >> this behavior should be investigated.
>
> >> Tom
>
> >> On 9/6/10 11:23 PM, G wrote:
>
> >> > I'm not receiving an oauth_verifier key/value pair in after the user
> >> > grants access through my app.
>
> >> > I'm receiving the at the URL specified in my app settings and in my
> >> > initial token request. The callback I'm getting looks like this
>
> >> >http://callback_url?oauth_token=xHddBl5uYQnSIESC4P16bmWS3ObDgMroXglEQ...
>
> >> > Every issue I have seen regarding this has to do with not supplying
> >> > callback url's. I have included them in every step. I have even tried
> >> > to use it when asking for user authorization which the tutorial here:
> >> >http://dev.twitter.com/pages/authsaysI don't need. I'm really at a
> >> > loss.
>
> >> > I have tried to use the PIN method as well, but again the above
> >> > tutorial falls short at the critical step of what to do when the PIN
> >> > is aquired.
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this 
> > group:http://groups.google.com/group/twitter-development-talk?hl=en

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk?hl=en

Reply via email to