Thank you very much!
Because I couldn't download the newer version of API and I only
checked the changelist of V1.3.1.0 yesterday, I thought that it is
still not being revised.

I update Picasa API in my project from V1.2.1.0 to V1.3.1.0, and this
bug is OK now.

On 1月9日, 下午5时17分, Frank Mantek <[email protected]> wrote:
> What version did you try this with?
>
> This bug:
>
> http://code.google.com/p/google-gdata/issues/detail?id=180
>
> was fixed for release 1.2.3.0, and i am using a password containing  
> lot's of special chars now in the unittests, so it is working for me.
>
> Can you verify that you are using 1.2.3.0 or later...?
>
> Frank Mantek
> Google
> On Jan 9, 2009, at 5:47 AM, voodoo_cat wrote:
>
>
>
> > I use .NET client library in my project. Now I find a bug.
>
> > If there is a character "%" in password, library will throw a
> > InvalidCredentialsException with message "Invalid Credential" even
> > login with right password.
> > For example, modify your password of Google to "%dddddddd", run
> > PhotoTool.exe in Google .NET client library sample, input your
> > username and password, you will get a InvalidCredentialsException.
>
> > Another phenomenon, if you input a password with substring "%1" and
> > the substring "%1" is not  in head of your password or in end of your
> > password, you will get a AuthenticationException with message "Error
> > authenticating (check service name): Unknown". No matter the password
> > is right or wrong.
>
> > It is very strange because I can't understand what the special point
> > is with the character "%".
>
> > Can anybody help me? Thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Picasa Web Albums API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Picasa-Data-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to