Uh oh...my downloaded resources have vanished!

When signing in, use Portrait Mode and Black on White colors. If password is typed wrong, all downloaded resources are lost.  I believe downloaded resources are kept if one does not attempt to sign back in.  I lost mine after typing in the wrong password.

I use the Kindle Fire and White on Black colors and / or Landscape Mode obscures the input box increasing the chance of an incorrect log in.

This happened to me last night when I signed on with my Nook Color (rooted). I had approx. 25 books downloaded to my SD micro card and one of them takes about 5 minutes to download. What I noticed when I was online with the Logos app for Android was that there was a downloading going on and it was a little long.

If I remember rightly, then things went dead. I quit the app and went back to it. Then I had to sign in again and it began the downloading process and said it was updating the library. Then I noticed I still had about 5 books on my Nook. The others were not there. So I figure...

that there was an update to some of the books and those would have to be downloaded again while the others did not have the update. It gave me a chance to download some different books and leave some others which got erased from the Nook. It was an opportunity to "refresh" or take another look at what I had available. So it is not all negative. I don't need to carry around a huge library on a portable machine. I have my computer at home for the real in-depth stuff.

I am supposing that I am correct in my "assessment" of what occurred though I may not be correct. That is for the experts to say.

Blessings to all,

Ergatees

Ahh - make that deleted the app.  Idefinitely wasn't delighted.

Dave

Same story here. I had dozens of books downloaded, all gone. Sigh.

Dave,

Alas, nothing was saved. Will have to spend SEVERAL hours to get things back on.

If it helps Logos any, here's the breakdown of what happened on my end.

Last night, was using my Kindle Fire at church (WiFI connected) and had full access to my resources. Put Kindle into sleep mode before leaving.

Arrived home, plugged in the Kindle for charging and turned it on for some bedtime reading (WiFI connected at home).

When Kindle woke up, was at the Logos app Home screen, with no devotionals at the top and when I entered my library, only had the "free account" resources available. Soon after resources started showing up (no progress bar seen at the top of the app), but devotionals still missing from Home screen. Noticed that resources no longer had the downloaded icon on them. Checked storage used on the Kindle and space was rapidly expanding as Logos was deleting the stored cache. [:'(] I was watching hours of d/l time disappearing!

Devotionals did not return to the Home screen until I re-logged into the app.

Like I mentioned earlier, I went nowhere near the login controls on the app until after everything had been erased by the app on its own.

Again, I must ask Logos to look into another way for us to add/keep our resources on our mobile devices. Thankfully I do not have bandwidth caps at home, but I DO have a time cap. [:(]

As much as I love Logos, the communication issues (iOS 5 update requiring complete reloading of d/l resources [warning was only AFTER the fact in the forums - never did see an official warning from Logos], lack of L3 support of new resources w/o warning when the decision was made [thanks for the later clarification Logos, but you would expect an announcement before, not after such an important decision] and now this "Logos have been silent but there has been an incident") are starting to leave a bad taste...

Could we have a statement from Logos on what happened please, together with details of the recommended way to get past this issue.

Some people in the thread seem to have trouble after re-logging in, whilst others find no problem.

I just want to know the safest way to proceed so I don't have to re-download my resources.

I'm a Kindle Fire user, and the same thing just happened to me right now. All my downloaded resources disappeared. I re-signed in and the app only recognizes the bible as downloaded to my device. I was curious, so I checked the storage and noted that it still looked pretty "full," so that got me even more curious. 

Plugged my fire into my mac and found the resources folder in the androidlogos directory. It's 3gb. So...are the files still there, yet somehow inaccessible? Anyone else notice this? Maybe we don't have to go through the problem/hassle of re-downloading...i'm really hoping that's the case.

It appears that I was luckier than most - I only had a handful (6-10) resources that disappeared. 

The thousands of resources I have painstakingly downloaded over the months have gone.

At least for me it was only a handful of resources, for me it seems to be linked to the Logos App logging me out.

My experience was about the same as Graham's, the only thing affected was the Logos App, the Bibles I had downloaded were still there (logos Bibles), because at Church this morning I forgot the password for the wi-fi, and only was able to use the Bible, and not a resource that I had previously downloaded. I would like to know from Logos, how that happens, why would all the other downloaded resources disappear, yet the Bibles didn't... seems unlogical to me.

Thanks in advance!

even manage what books are downloaded to your mobile device from within Logos 4 or via the web site.

Wow! Can't wait. This would be a tremendous help!

I also know this is a risk I take in running a sub-v1 or Beta application.

That is commendable, but the problem happened because of server upgrade and I'm sure that we would like to have known in advance, and be assured that steps will be taken to eliminate the problem in the future. I didn't see any issue on the iOS forum...

I agree.  I completely understand the need for server upgrades, but a reset of downloaded resources, as well as not (yet) having a way to bulk download the ones we want, is what makes this so frustrating.  Along with not being notified.  If I'm going to reset a main server at my job, where I work IT, especially if it's during the day, I email people to let them know.  A few people may get annoyed with the extra communication, but most would rather know beforehand.

Thanks for working on this, Logos.  I think you have the best Bible software out there in terms of available books and potential.  I've invested quite a bit between base packages and commentary upgrades and so on.  But being confident I can access those books with a minimum of hassle is a deciding factor between you being my source for all my future theology resource purchases, or just a few. Thanks for all the features you have added and I look forward to future additions, like split-screen viewing and eventually notes/highlighting.

Really? The first assumption is that we're lying to you, and making up technical excuses for an intentional deletion of cookies and increased user inconvenience, just so we can avoid Android users sharing resource files that we leave up on an FTP server anyway? Sigh...

We hate forcing users to re-log in. It's not in our interests, ever. So we avoid it at all costs. However, a recently discovered attack vector on cookie authentication led to an update of Microsoft (and others') server platform that changed how encryption on authentication cookies worked. We were compelled (by Visa/Mastercard PCI security compliance procedures -- and common sense!) to update our servers. 

Thank you for the reply Mr. Pritchett.

My apologies for how my comment was taken. I wasn't assuming individuals were lying, but based on what was being released from Logos, that the fullness of the story wasn't coming to light. Whether it was a breakdown between the boots on the ground and commanders up top, or any number of things that can go wrong between the reporter and the technician, it just did not seem to make a lot of sense to me with how it was being reported. It was wrong for me to assume that you did not have the fullness of the story to report.

I'm in IT, and I know that many times when there is an emergency server outage notification or whatnot going out to employees (or even when we get a notification from our colo...), the notification is somehow represented as something that is not as particularly spot on as it could have been. This is mostly due to the fact that there is a language barrier between IT and non-IT, or that IT just doesn't want to go into the amount of detail that could be released.

We knew the re-log in was coming, but the people who update the server had no idea it would force the re-download on Android. 

No QA or mock go-live? I know, being in IT, you can't test everything, but this change seems to have been a big enough as well as cause a consistent enough problem that it should have been spotted. Especially if it was known that it would cause a re-log in. If anything, I guess there will be a post-mortem (Good times... important meetings on a Monday).

We knew the re-log in was coming, but the people who update the server had no idea it would force the re-download on Android. 

We don't anticipate that cookies will be reset for a very long time, but clearly we can be forced into it. So we're changing the app to check if you're logging in under the same account you'd most previously used, in which case we won't delete the stored book files. (Arguably, it should have been done this way the first time, but you can't always anticipate every scenario.)

Ultimately, we're implementing a model where "download to this device" is a server-synced property that survives log ins, log outs, etc. and is easily manged from inside Logos 4, inside the mobile app, or at Logos.com. This is partially coded, but just hasn't been finished and shipped yet. It will make this scenario and problem irrelevant.

These sound like very good plans. I can't wait until they are live. Until then I'm very leery of going through the process of downloading all the resources I had on my device previously without a greater level of assurance that they should stay there for a while.

Like I said before, I know that things like this taking place is the risk I take in running a sub-v1 or Beta application... I am grateful that Logos is developing an Android application, and also the impact Logos as a Bible study application has had on my studies.

Keep up the good work, LBS developing a good product, that has me heavily invested in, and that I use daily.

Regards,

Ryan