Logos 10 loses my books

I'm also having the same issue on my Android phone where all the books which I've purchased are no longer downloadable stating that it's not part of my Logos Library. They can only be read while online. Only books which I've downloaded previously before the update are readable offline. I think Logos made a big blunder with the Android app. I've raised a ticket on this matter. It's disappointing that Logos did not do a better quality control before releasing the latest version for Android. Edit: In case, it's necessary I have also added for the example below, my order number 25664217.

I am guessing this is caused by purchasing the wrong upgrade. I think is you purchase a library upgrade instead of a feature upgrade, it screws up your library. Just a educated guess..I say this because there are two different LOGOS 10 purchase paths, feature upgrade, and library upgrade. 

I have the same problem on IOS. I have not purchased a Logos 10 upgrade, however my entire library is not available and many which say ”you already own this product” on the website is not available on the new redesigned mobile app (but were in the previous edition). For example, the Eastern Orthodox Bible (EOB) is not available for the mobile app for me, but is shown as purchased. Another is “Commentary on Saint John the Apostle and Evangelist: Homilies 1–47” published by Catholic University of America shows as purchased on the website but not the mobile app.

Yes I do not see that indicator option either.  You could filter by 'Not Downloaded' then could click on the indicator to download resource

Hi Ali,
I was not able to figure out how to do the rebuild index on the app for iphone. The image didn’t help as it looks different than the iphone layout. I tried typing it in in several different places but it did a word search in the resource instead of bringing up a command option. I might be in the wrong spot. However, I did a library sync in the options, and that fixed the issue. As far as I know all of my resources are available on my phone again. I did not realize this step was necessary. The update was done automatically through automatic updates, and I just noticed that resources I was using previously on my phone were no longer available when I went to use them again.

Hi,  are they still working on the fix for Android?

Glad this is a known issue and working to fix it. I sent an email 4 days ago as I had same issue but I've received any acknowledgement or replies.

Having the same issue here.

When selecting books 'Mortal Fire' which I recently acquired is at the top of the list as in my library.

Then, the I select info about this book I'm met with the message: "This book is only available online because it is not part of your Logos Software library. Learn more at Logos.com"

Same issue for me.  I'm on Android 12 and only resources that I downloaded prior to the update are available offline.  Sync does not work for me.  Based on prior comments, it's probably not a good idea to uninstall and reinstall since you will lose all of your downloaded resources.  Hopefully this is a high priority to fix.  Thanks advance for working on this.

Here is my experience of the problem:  When seeking to download to my Android phone any of the resources that I definitely own – and are already stored on my Windows computer running Logos 8, but have not as yet been saved to my smartphone – I receive this message: “This book is only available online because it is not part of your Logos Bible Software library.”  All books previously downloaded and secure on my phone continue to be available for offline access, but not the rest of the library that I have purchased.  This is very puzzling.

It seems that many other users, who previously had no such issue, are now experiencing similar difficulties and so apparently something is amiss with the updated Android app itself and they are not caused, e.g., by logging in problems.

As I constantly use Logos on my phone, the alternative of tardy online retrieval of material is, I am sure you will understand, an extremely frustrating and gloomy prospect and is manifestly completely unsatisfactory.

Please, please; this bug needs to be fixed … and urgently.  Break out the insect spray and oil the rusty lock on the invaluable, incomparable Logos treasure chest!

(The urgency and personal importance of this issue may be gauged by the fact that this is the very first time I have ever posted on any internet forum in over a quarter of a century online.)

Glad to know it wasn't just me. I just recently changed Phones, and noticed that my latest Phone (Google Pixel 7 Pro) was experiencing the same issue as everyone else here. Hopefully, a fix is released soon. Thank you for your efforts!

I have the NKJV bible on Android in Logos 10, but not online in the web app or in the windows version.It may be that inclusion in the Android app was itself a bug, so I purchased the NKJV this morning.

Stephen Rybacki said:

I'd sure hate to think Faithlife does things this way, especially since many people have a significant investment.

I hate to tell you, but this is actually a recommendation by nameless forum participants ... fast development, ship it and fix it.

Normally I'm not uncomfortable with that; 'fix it' usually is pretty quick (sometimes hours).  But the L10 ship (for me) was/is a major kludge.  Both the mobiles and the desktop have major bugs, and limited communication from bug-HQ ... this AM I felt sorry for Ali, starting so early.

DMB said:

Stephen Rybacki said:

I'd sure hate to think Faithlife does things this way, especially since many people have a significant investment.

I hate to tell you, but this is actually a recommendation by nameless forum participants ... fast development, ship it and fix it.

Normally I'm not uncomfortable with that; 'fix it' usually is pretty quick (sometimes hours).  But the L10 ship (for me) was/is a major kludge.  Both the mobiles and the desktop have major bugs, and limited communication from bug-HQ ... this AM I felt sorry for Ali, starting so early.

I guess I'm old school, but every application I ever wrote was thoroughly tested on all platforms it could run on by an independent tester whose job it was to break it until they couldn't anymore.  I'm sure that it'll get fixed, but "what if" the fix isn't possible at all?  I've seen this before and it has killed lesser developers.

[U]

MJ. Smith said:

Unfortunately, the Android platform is harder to run public betas on. While there were a few known problems and incomplete features in the RC's, this release has gone relatively smoothly. Have you worked with people who programmed for ATM's or MRI machines? If you do, you know that no commercial public software comes close to a zero error rate policy. I spent decades on payroll/personnel applications with 30,000+ critics twice a month, I know something about accuracy and stability. However, we had much more control over the platforms on which the applications had to perform. FL is a small company with a history of less than perfect testing and less than completed features. But can we keep the expectations and complaints realistic? I've spent 4 hours at night with a Chinese programmer tracking down a failure in a major XML editor. For several years, I could crash Microsoft Word at will. The "unable to break it" rule is highly dependent on the skill and imagination of the tester.

Yeah, I believe you.  It's useless to complain about it, and I know it.  This is one of the reasons I got out of development to become a full time data engineer.  The industry has definitely passed me by and I have no regrets switching fields back in 2010.  I guess you could say I saw the handwriting on the wall [;)]

MJ. Smith said:

While there were a few known problems and incomplete features in the RC's, this release has gone relatively smoothly....

I hate to disagree MJ but I think the quality of the final product Android is fairly poor. There are a number of fairly serious issue which are easily identified by end users and materially affect the products function. For instance, books cannot be downloaded, many functions relying on the library don't work throughout the app. I'm pretty disappointed by the quality of what has been shipped compared to the desktop version.

Plus there is a host of more minor issue which should have been identified in the QA process too. It's not reasonable to expect perfection however the number of bugs creeping through seems substantially above what I think users ought to bear. For me parts of the app are rendered unusable for some users.

Thanks for the comments James. For reference my second install manifested the same issue. I too have experienced far worse in apps, however for an app that costs as much as logos, with > 1m installs etc I think the quality isn't at the desired level, certainly from my user experience. It is probably worth noting that the vast majority of issues reported on this forum to Faithlife regarding the Android App are met with a confirmation that the issue can be reproduced and wil be fixed. That tells us that these are not hard to find issues but are straightforward to repro. In essence the Logos QA effort didn't pick up a whole number of issues in the final build.  Hence my comments...

I agree Darren!