Sounds obvious, but in my experience the most common reason for a 401 from the server with Google APIs is getting the service name wrong. This is especially common when folks copy existing auth code fragments to get something working - at least it did with me!
For reader I believe the service name should be 'reader' On Mar 26, 5:16 pm, Chris Stewart <cstewart...@gmail.com> wrote: > I've found various sources online trying to do this but every example I > found hasn't worked for me. Most simply return 401 errors from the server. > > I've gotten the auth token needed to make the calls from the local accounts > on the phone and I've also tried making the ClientLogin call specifically > with my username and password, and either way they're returning 401s. > > So, has anyone been successful in getting unread Google Reader posts? Extra > credit if you're doing it without having to handle a user's Google Account > credentials first hand, but are doing it through allowed permissions. > > -- > Chris Stewarthttp://chriswstewart.com -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
