Authentication issues in Android Reader apps 4.4.1+

Some users are reporting repeated sign in requests after upgrading to the Android Reader Suite apps with Android account management support (version 4.4.1+). Please report any issues you have with sign-in / authentication in this post.

It's important that you include app version and your device type when reporting issues.

Thanks for your help beta testing this new feature.

Find more posts tagged with

Comments

Gabe Martin

We've built a new test version of the apps to get additional log info to further troubleshoot sign in issues people are experiencing.

If you are seeing repeated sign in request in the 4.4.1 app please install one of the following test builds and send logs. So far issues appear to be specific to Samsung Galaxy Tab devices.

4.4.2 test builds with additional logging:

Bible 4.4.2 (build 232)

Vyrso 4.4.2 (build 232)

Erwin Stull, Sr.

I sent the l8gs from the new build a few minutes ago. Unable to attach here on the forum.

Drew Hannay

I believe we've figured it out!

If your device time is off by more than a few minutes, part of the sign in process will fail (the server rejects the request as invalid). The upside of this is that it makes the login process much more secure...the downside is that Android devices (especially tablets) can easily "drift" away from the current time.

The workaround: Try setting your device time to "Use network-provided time" if it isn't already. Otherwise, try setting the time on your tablet to exactly match the time on your phone. After updating your device time, try signing in again in the Logos app. You may need to enter your credentials twice, but after that you should be signed in and good to go (no more sign in dialog).

Please let me know if this works for those of you who are affected. We will implement a better solution on our end on Tuesday after the Labor Day weekend and get another beta out with the fix.

Thanks for all your help and I apologize again for the inconvenience this has caused you.

(‾◡◝)

My tablet was off by 5 minutes so I manually reset it and it seems to have worked for me. Thnx.

Randy Lane

I believe we've figured it out!

If your device time is off by more than a few minutes, part of the sign in process will fail (the server rejects the request as invalid). The upside of this is that it makes the login process much more secure...the downside is that Android devices (especially tablets) can easily "drift" away from the current time.

The workaround: Try setting your device time to "Use network-provided time" if it isn't already. Otherwise, try setting the time on your tablet to exactly match the time on your phone. After updating your device time, try signing in again in the Logos app. You may need to enter your credentials twice, but after that you should be signed in and good to go (no more sign in dialog).

Please let me know if this works for those of you who are affected. We will implement a better solution on our end on Tuesday after the Labor Day weekend and get another beta out with the fix.

Thanks for all your help and I apologize again for the inconvenience this has caused you.

This worked for me on Samsung Galaxy Note 10.1 2014 Edition.

Erwin Stull, Sr.

Drew and team; I am sure and confident that the time difference problem is the root cause of the sign-in issue. So far, everyone that was bit by this bug has recovered using your work-around. Thanks.

The blessing in this (there is a hidden blessing in everything) is that it has uncovered a potential problem with Tablets and other devices that do not update the time automatically by NTP or GPS. So now, I am looking for solutions to auto-sync the time (without rooting). Hopefully, this issue is prominent enough (I know, that sounds like a curse, but it's not) that manufacturers of devices will make auto-syncing the time on devices a basic feature of every device of this type. [:)]

Mike Measley

So far issues appear to be specific to Samsung Galaxy Tab devices

I had the issue over the weekend with my nexus 7. I needed my tablet for church so uninstalled and reinstalled stable version.

Mike Measley

Had to turn off network time on nexus 7 and enter the time manually. Then the 4.4.2 version loaded without the sign in error