verify_credentials verifying regardless of credentials?!

[FrankieShakes]

Hey all,

I've been trying to integrate the verify_credentials call into my
Dashboard widget but have noticed that regardless of which password I
use with my account name, Twitter seems to return a "authenticated:
true".

Has anyone else experienced this? I'm not sure what the cause might
be, but I suspect it's isolated to me. Any ideas what could be
causing this?

Also, another thing I noticed is that in order to make successful API
calls, the username can't be the user's email address:

ie: my-twitter-username rather than my-e...@gmail.com.

Is this a known issue?


TIA,
Frank

[Tapos Pal]

Hi Frank,
I think you are trying to develop the application in your local machine and already you are login at twitter. so when you want to verify credentials this always return true.

--
Best Regards,
Tapos Pal
http://tapos.wordpress.com

[FrankieShakes]

Hey Tapos,

The weird thing that it returns true even after making a call to
"http://twitter.com/account/end_session".

Any ideas on what else I can do to try and prevent this from occurring
on my machine?


Thanks,
Frank

On Mar 16, 10:59 am, "Tapos Pal" <tapaspa...@gmail.com> wrote:
> Hi Frank,
> I think you are trying to develop the application in your local machine and
> already you are login at twitter. so when you want to verify credentials
> this always return true.
>
>
>
> On Sun, Mar 16, 2008 at 8:07 PM, FrankieShakes <frankma...@gmail.com> wrote:
>
> > Hey all,
>
> > I've been trying to integrate the verify_credentials call into my
> > Dashboard widget but have noticed that regardless of which password I
> > use with my account name, Twitter seems to return a "authenticated:
> > true".
>
> > Has anyone else experienced this?  I'm not sure what the cause might
> > be, but I suspect it's isolated to me.  Any ideas what could be
> > causing this?
>
> > Also, another thing I noticed is that in order to make successful API
> > calls, the username can't be the user's email address:
>

> > ie: my-twitter-username rather than my-em...@gmail.com.

[Marco Kaiser]

Hey,

just for information, verify_credentials is working for me as expected (using XML).

Marco

[Frank Manno]

Hey Marco,

I haven't tried XML... I'll give that a shot. Just curious, are you
using XML with a widget?

Thanks,
-f

--
- Frank
FrankManno.com

[Marco Kaiser]

No, from an AIR application (twhirl).

[FrankieShakes]

So I've gone ahead and tried the XML response as well... Regardless of
what credentials I pass, I always get a "verified = true" response.

Can anyone figure out why I'm always verified? Is it something
Dashboard-related? I'm stumped on this one...

Any help would be greatly appreciated.


Thanks,
-f

On Mar 19, 8:27 am, "Marco Kaiser" <kaiser.ma...@gmail.com> wrote:
> No, from an AIR application (twhirl).
>

> On Wed, Mar 19, 2008 at 1:23 PM, Frank Manno <frankma...@gmail.com> wrote:
>
> > Hey Marco,
>
> > I haven't tried XML... I'll give that a shot. Just curious, are you
> > using XML with a widget?
>
> > Thanks,
> > -f
>

> > On Wed, Mar 19, 2008 at 5:10 AM, Marco Kaiser <kaiser.ma...@gmail.com>

> > wrote:
> > > Hey,
>
> > > just for information, verify_credentials is working for me as expected
> > > (using XML).
>
> > > Marco
>

> > > On Wed, Mar 19, 2008 at 12:31 AM, FrankieShakes <frankma...@gmail.com>

[bkly...@gmail.com]

I think it is dashboard related. I'm writing a dashboard widget as
well and it seems to be the cache being held by the engine. I didn't
find a good way around it other than to inform a user that "Changes to
your username and password will not take effect until the next
reboot."

Good luck.