Lost all books with password change
Hi,
I changed my password on Logos, and when I try to enter my new password on my iPad app, I had to re-download all my books.
Comments
-
Hi Jack,
This is a known issue that has already been entered as a bug - sorry that it's not yet fixed.
0 -
Kevin ... you can't be serious? In these days of security, everyone recommending changing your password often, etc. it's a known bug?
What's the next surprise?
Shouldn't you let users know?
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Shouldn't you let users know?
https://community.logos.com/forums/p/88716/624121.aspx
That's not letting the users know, generally. But there's some info out there.
-Donnie
0 -
Mucho-ish years back, I started my (very) limited conversation with Bob on 'honesty'. He interpreted it within cultural America (meets exacting requirements). I interpreted it within what you tell your friends or kids.
But I very much appreciate apps that are honest. One I really like had an update that said they'd detached my stylus support but were fixing something else. 'Don't update!'. I liked that. It was honest. Another one lists fixed and not fixed. My current one that blows up my iPad did indeed warn users. Honesty is healthy and invites trust.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Honesty is healthy and invites trust.
Out of curiosity, then... I believe that Faithlife didn't know about the bug in the iOS app until I reported it on Sep 3, 2014 (based on the thread I linked to earlier in this thread and Kevin Byford's response).
What should Faithlife's response have been (in the interim between acknowledging the bug and fixing it, whenever that happens)? How quickly ought that to have happened? What are the criteria by which Faithlife decides which bugs need such honest communication?
I don't believe or have any sense that Faithlife is being dishonest in communication about this bug. My concern is that the mobile apps seem to be second class citizens in the Faithlife ecosystem. I base this assessment on two factors: a) Some direct personal interaction with Faithlife employees earlier this year. I don't think they were saying this explicitly, but based on what was said, I'm inferring such an attitude on Faithlife's part. b) The features and functionality that are found in new releases of the mobile apps. There have requests for years for better offline functionality, on par with other "Bible study" mobile apps. The bug we're discussing here and other bugs seem to remain for release after release after release. I don't recall Bob ever jumping in to the mobile forums and asking what big new features we'd like to see in the mobile apps.
I admit that my assessment may be incorrect. I'd love to see evidence that proves me wrong. But this is my sense right now, and it is why I stated in another thread that I'd be willing to pay for the mobile app (e.g. $19.95 or whatever) if it would get the mobile apps more attention.
My $.02 ...
Donnie
0 -
Sept 3??? That's even worse. We're talking THREE MONTHS??
You believe Faithlife didn't know about the bug?? Do they use 'Bible' software? Romance software maybe? OK, greek gods software? Any of their apps?? I'd suspect there's a decent chance if they use at least one of them.
What should Faithlife's response have been? Well, gee. That is a toughy. Maybe they could copy other app company's and 'communicate' (app update text, in-app notes, site notes, ... the list goes on). Quite frankly none of my other apps do such a poor job of communicating.
And Donnie ... your opinion is worth far more than 2 cents! And consistently good.
EXTRA: I notice quite a number of my apps are now 'badging' within their apps to direct you to what they fixed, what's still a challenge, what's on the horizon, etc. Quite commendable.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Sept 3??? That's even worse. We're talking THREE MONTHS??
*That* is what I'm unhappy about. I wouldn't even worry about "communication" if they would fix a bug like this in a timely fashion. I don't have any indication that they knew about the bug before I pointed it out. The questions Kevin asked make me think it was news to them. It's even possible that it was a regression from a previous release. I'm willing to give Faithlife the benefit of the doubt on the existence of the bug.
Many open source software projects have their entire bug database visible online. I'm not sure that is realistic or feasible for Faithlife. So I'm not sure what the best response would have been, communication-wise, or the conditions under which such communication is required.
I have an idea: FIX THE BUGS!!!
Donnie
0 -
I can see the merits of actually fixing a major bug (versus warning people about not fixing it).
I guess I'm thinking along the lines of this example.
Let's say the steps outside your kitchen door are broken and someone could fall down and get hurt.
But let's also say, that step-fixing is not scheduled until mid-2015 or so. I'm just arguing that a sticky note on the back door might be helpful.
And yes, I'm joking. You're right.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Let's say the steps outside your kitchen door are broken and someone could fall down and get hurt.
Something about a railing on your roof would work quite nicely here...
:-)
Eating a steady diet of government cheese, and living in a van down by the river.
0 -
I believe that Faithlife didn't know about the bug in the iOS app until I reported it on Sep 3, 2014 (based on the thread I linked to earlier in this thread and Kevin Byford's response).
I can confirm Faithlife didn't know about the bug until you reported it. I left the team shortly after that though, so I can't really speak to why it hasn't been fixed. I completely agree that it's a major issue though and deserves immediate attention.
0 -
This issue is being looked at by the server team.
0 -
This issue is being looked at by the server team.
Should we infer from your comment that the bug is not in the iOS app itself but on the server side?
I know similar challenges were experienced during the server outage, but my issue wasn't related to a server problem - it was related to a password change (with no failed logins). With my techie hat on, if this were a server-side issue, that would seem to imply that the server returned something to the app that made the app go into "new install" mode. Interesting to think about that... (Just thinking out loud, in case it's not obvious.)
Donnie
0 -
Should we infer from your comment that the bug is not in the iOS app itself but on the server side?
Yes, the bug is not in the iOS app itself.
0
