problem on a fresh new install (can't sync)

[Yoav]

Hi,

I've just installed ReaderScope on my Nexus One.
When I try to load/sync it for the first time, I keep getting this
error message:
"Error downloading Tags: [-1: com.altcanvas.asocial.HttpException]"

My network is fine (both WiFi and 3G, tested with many other apps on
the same phone), what am I missing or doing wrong?

[Jayesh Salvi]

Are you using AutoLogin or username/password?

Have you tried both methods?

Can you send me the logs? (Settings > Logs, then Menu > Email)
--
Jayesh

[Jayesh Salvi]

--
Jayesh

On Mon, Mar 15, 2010 at 3:54 PM, Jayesh Salvi <jayes...@gmail.com> wrote:

Are you using AutoLogin or username/password?

I guess you wouldn't know what I meant by above question. ReaderScope automatically tries to log you in using the Google account stored in phone. But you can use username/password combo too. You can go to Settings > Credentials Management > Logout. Next time you start, you will be taken to login screen. There you can enter username password.

I am not sure if this is what is wrong. I still suspect there is some networking problem. But we can try this to debug the problem.

In the v1.8.3a I have turned off the automatic AutoLogin, so users would know which login mechanism they are using in case a problem arises.

Let me know what you find out.
Thanks.

[Yoav]

Thanks for the quick response and deep explanation!
I'm not THAT a noob, so i know what auto login means - and actually,
that's one of the reasons I've decided to try this client instead of
NewsRob :)

Anyway, the logs have the exact error message, over and over again.
One time I also got "java.net.SocketException: The connection was
reset", but that's it..
I can try to manually login, but that would miss the point for me :/
Any other ideas? or you want me to try the manual method to see if
that works?

On Mar 15, 4:57 pm, Jayesh Salvi <jayeshsa...@gmail.com> wrote:
> --
> Jayesh
>

[Jayesh Salvi]

--
Jayesh

On Tue, Mar 16, 2010 at 2:07 PM, Yoav <yoa...@gmail.com> wrote:

Thanks for the quick response and deep explanation!
I'm not THAT a noob, so i know what auto login means - and actually,
that's one of the reasons I've decided to try this client instead of
NewsRob :)

Anyway, the logs have the exact error message, over and over again.
One time I also got "java.net.SocketException: The connection was
reset", but that's it..
I can try to manually login, but that would miss the point for me :/
Any other ideas? or you want me to try the manual method to see if
that works?

The error messages you mention mostly indicate network access problems. I asked about trying another login mechanism because that's the only major change in recent releases and AutoLogin is not tested on all modern Android versions (including Nexus One). 

Let me know what you find.

[Yoav]

ok, we have some progress here:
I used the manual login and it worked perfectly on the first try -
which means it's really not a network problem.. so why can't I login
using the built-in google authentication credentials?

[Jayesh Salvi]

--
Jayesh

On Wed, Mar 17, 2010 at 2:43 PM, Yoav <yoa...@gmail.com> wrote:

ok, we have some progress here:
I used the manual login and it worked perfectly on the first try -
which means it's really not a network problem.. so why can't I login
using the built-in google authentication credentials?

AutoLogin is implemented with a library that is not supported and not documented by Google. But I provide it as an alternative for users who hesitate to give away their username/password. The library was working fine for old method of authentication. But the new changes in authentication seem to not work. AutoLogin is reported to be working on Android 1.6 devices and also someone reported it worked for them on 2.0 device too. But because we don't know the insides of the AutoLogin library, I cannot confidently say it will work on all devices.

You can get more details on the issue in this blog post: http://jyro.blogspot.com/2010/03/readerscope-1823-new-authentication-and.html

There is an official API on 2.0 devices to achieve this. But it is still unclear and requires a phone with 2.0 ROM, which I don't have access to right now. I will try in future to leverage this official API to make AutoLogin work again. But till then I would advise you to use username/login mechanism. (FWIW, the password is not stored in plain text, but is encoded before saving on the device).

HTH.