BUG: Behavior after changing password
I finally overcame my laziness and changed my Logos / Vyrso / Faithlife password last night. Incidentally, this is in response to the massive password theft that was recently announced and which has begun to be used to attempt break-ins at other sites.
I have 2 iPads with the Bible app that use this account. One is an iPad 2 on iOS 6 and an older version of Bible. The other is an iPad 4 with the latest version of iOS and Bible. They both behaved the same way.
As a user, I don't expect that changing my password should result in a massive change. Intuitively, I would expect to have to re-confirm my credentials and go on my merry way. This was not what happened. Instead, it was a fairly painful process of re-loading my library information and waiting for who knows what before my library looked like it had before the change.
My impression is that the Bible app treats *any* login as if the app had just been (re-)installed, and it goes through an initialization process to get into a useful state. It wasn't completely like that - my documents were there, and my most open resource ("Read") was still there. But the library was treated as if it were being freshly discovered.
There was no need for this. It was the same account. Nothing had changed. The effect of this was that my the app was nearly unusable for quite a while. My wife's study was halted for a couple of hours because resources she had been used to reading were no longer showing as being in the library. I'm not sure what happened that made the resources finally show up - there was no indication of network activity, or the "indexing" progress bar, or anything like that.
I'd like to suggest that this process be made a little more intelligent. If a login is to the same account that had previously been logged in, I don't think the app needs to do anything. It should just leave things as they were and allow the user to use the app immediately.
Thanks,
Donnie
Comments
-
As a user, I don't expect that changing my password should result in a massive change.
Agreed!
I don't think much time has been spent on this issue since users rarely change their passwords, and the app is designed for a single log in.
Did you delete the app and do a complete reinstall or no?
0 -
If a login is to the same account that had previously been logged in, I don't think the app needs to do anything. It should just leave things as they were and allow the user to use the app immediately.
Agreed! Hopefully, the iOS team can be freed up from implementing infrastructure support features to be able to work on UI experience issues like this (and font selection [;)] ).
MacBook Pro (2019), ThinkPad E540
0 -
I just talked to James about this and there's definitely a bug here. Donnie, do you happen to remember if you typed your password incorrectly at first when reauthenticating? We think the bug is that when you type your password incorrectly, the app sends a "sign out" message and wipes your data. That certainly shouldn't happen, but it would be nice to know the scope of the bug (meaning, does it wipe your data even if you type your password correctly the first time).
On Android, when reauthenticating, we require that the same user sign in as was previously signed in, so we don't even have a way of signing in as a new user (so no data can get wiped). On iOS, you could technically sign in as a new user when the sign in dialog is presented, which is why the data-wiping code is there. I think we probably want to make iOS behave the same way as Android, because it's extremely difficult to make sure everything gets reset for a new user without uninstalling and reinstalling the app.
I'll make sure a case is written up, if there isn't one already.
0 -
Did you delete the app and do a complete reinstall or no?
No. Just started the app and, since it was online, it immediately prompted me for credentials, with my email address pre-filled.
Donnie
0 -
Donnie, do you happen to remember if you typed your password incorrectly at first when reauthenticating?
Drew,
Thanks for the response. To answer your question, I definitely entered my password ***correctly*** on both iPads. I just started the app and, since it was online, it immediately prompted me for credentials, with my email address pre-filled. After entering the password once, I was *not* re-prompted. I ended up on the "Read" screen (both times), at which point going to "Library" revealed the issue.
Hope this helps. Thanks again,
Donnie
0 -
-
More information...
It had been a few hours since I'd used Bible on my iPad, and when I went into it, I noticed that my Library was still not correct. I killed the app (not uninstalled) and restarted it. This time, when I went to Library, the message was "Cancel All Downloads" (implying downloads were in progress) and the network spinner was going (confirming that implication). It ran for 30+ minutes before the downloads seem to have completed.
However, my Library still isn't displaying correctly. I've been preaching through Acts for over a year. If I use the single word "acts" as a filter in the Library, I used to get upwards of 100 resources listed. Now I get 24. There are specific ones I would read regularly which aren't in the list right now. Apart from re-installing, which would not quite be torture but close
, I don't know of a way to force the library to "index" (with the associated progress bar I've seen on occasion - something I've not seen since changing my password). The total (unfiltered) resource count does look correct - > 6,200.I really need to get this fixed. I depend on this for a large chunk of my seminary reading and my weekly study.
Thanks for the assistance, folks.
Donnie
0 -
I don't know of a way to force the library to "index"
From the Home page, enter "rebuild index" (lowercase, no quotes) in the Reference field at the top. Please let me know if that solves the issue.
0 -
-
How many downloaded resources did (do) you have?
I don't know for sure. Total downloaded resources, probably a couple hundred. Downloaded resources in my "acts" results list, maybe 10.
Donnie
0 -
From the Home page, enter "rebuild index" (lowercase, no quotes) in the Reference field at the top. Please let me know if that solves the issue.
That seems to have done the trick. 135 results for "acts" in my library.
NOTE: The index did not rebuild until I killed and restarted the app. I'm not sure if you expected that or not, but you didn't mention it in your instructions.
Thanks much!
Donnie
0 -
NOTE: The index did not rebuild until I killed and restarted the app.
This is probably a result of the password change issue - I'll make sure it's in the case.
0 -
Encountered much the same problem again today, based on no changes on my end.
See: https://community.logos.com/forums/t/92013.aspx
-Donnie
0
