Hey,

The authenticate flow will display a login screen in a number of situations:

* if the user isn't logged into twitter.com
* if the user hasn't allowed the application access to their account before
* if you pass the force_login or screen_name parameter to the authenticate
endpoint
* if the user has revoked access to the application
* if the requested permission level is different to the one the user
originally allowed

Is it possible any of those situations are happening?

Best,
@themattharris <https://twitter.com/intent/follow?screen_name=themattharris>
Developer Advocate, Twitter



On Wed, Jun 22, 2011 at 6:14 AM, mike_f1 <[email protected]> wrote:

> I have the exact same issue, but am using C# and the Twitterizer library.
>
> Also, I can't seem to prevent the Authenticate pop up appearing and asking
> for permission despite the app already being authorised for this user and
> the user already signed in to Twitter. Checked by logging into twitter and
> going to Applications - I 'allowed' it by using Authenticate as per
> http://dev.twitter.com/pages/sign_in_with_twitter the first time, but it
> still pops up every time since.
>
> Is it something to do with how the App has been 'allowed' access? Do I need
> to 'allow' the app using the authorize URL first then using the authenticate
> url for future requests?
>
> Must be doing something wrong but I can't see what, can anyone shine any
> light on this please?
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Reply via email to