Bible! app is now unusable

I think I might be having the same issues described here: https://community.logos.com/forums/t/93721.aspx .

- iPad Air 2 128GB wifi- Latest version of the Bible! app (I'd look in the app, but it hangs before I can get there - according to the App Store, 4.3.7 installed on Oct 28)
- iOS 8.1

When I start the app, it displays the "Missing Resources - Cancel / Download" message. If I hit "Download", the app becomes unresponsive nearly immediately; and there's no sign that any books ever get downloaded. If I go back to the main iOS screen and then another app, when I come back the Bible! app has stopped / crashed. If I hit "Cancel" when I start the app, I can get to the side menu (usually). Typically I then go to "Documents" and try to bring up a reading plan. That just results in the large spinner in the middle of the screen; and it never returns. It frequently crashes if I just wait there. But usually I don't want to wait indefinitely, so I go to something else on the iPad. When I come back, the app has crashed.

I'm not sure why things are so fragile all of a sudden. Perhaps it's the confluence of: switching to a new device; iOS 8.1; and all the resource updates to support L6. I know I'm not paying for the app, but it seems that Faithlife is making some representation that it will actually work. It's become an integral part of my day and week, supporting my seminary studies and sermon preparation.

Question: Does a particular Bible! app installation (e.g. this one I'm describing here) require that there be a corresponding entry in my "Manage Devices" page under my account on the web site? If so, what is the expected behavior if there is *not* such an entry? Because that's the situation I have: none of the iPads on which I have the app installed are listed under "Manage Devices"? Why wouldn't a successful login of the app add an entry if it doesn't find one? It doesn't seem reasonable that an installation of the app that is working properly should stop functioning if its corresponding device under "Manage Devices" is missing or unavailable?

Any chance of some help on a Saturday? Thanks,

Donnie

Find more posts tagged with

Mobile App

Comments

Graham Criddle

Hi Donnie.

When I start the app, it displays the "Missing Resources - Cancel / Download" message.

If you go to the iOS setting menu and scroll down you will see "Logos Bible" as one of the apps. There is an option there to "Start at Homepage". I'm not sure if that will help at all but could be worth trying.

Perhaps it's the confluence of: switching to a new device; iOS 8.1; and all the resource updates to support L6.

There certainly seem to have been a number of issues with 8.1 and updated documents. It seems to be running fine on my iPad with 8.0.2

Does a particular Bible! app installation (e.g. this one I'm describing here) require that there be a corresponding entry in my "Manage Devices" page under my account on the web site?

I don't know if it is required but it would certainly be expected. Most people report multiple entries (a new one seems to be created with iOS updates I believe)

If so, what is the expected behavior if there is *not* such an entry? Because that's the situation I have: none of the iPads on which I have the app installed are listed under "Manage Devices"?

I don't know but I wouldn't expect it to cause the problems you are seeing.

Why wouldn't a successful login of the app add an entry if it doesn't find one?

It should do.

Have you tried installing a different Logos app - such as Verbum - and logging into that using your standard credentials.

That may / should do a few things:

It might create a new "Manage Device" entry
It won't be setup to download lots of resources and so you wouldn't hit the "Missing Resources" issue

Not sure if any of this will help but the best I can think of at the moment

Graham

Donnie Hale

https://community.logos.com/discussion/comment/650591#Comment_650591

Have you tried installing a different Logos app - such as Verbum - and logging into that using your standard credentials.

That may / should do a few things:

It might create a new "Manage Device" entry

It won't be setup to download lots of resources and so you wouldn't hit the "Missing Resources" issue

Thanks for the reply, Graham. I have not tried that. I have a question about that idea...

If a new device entry were created, would that same entry be used for the Bible! app? Or are the entries specific to the combination of device+app?

Thanks again,

Donnie

Graham Criddle

https://community.logos.com/discussion/comment/650593#Comment_650593

If a new device entry were created, would that same entry be used for the Bible! app? Or are the entries specific to the combination of device+app?

I would expect that - in this scenario - a new entry would be created that wouldn't include the existing Bible! app

Normally when an entry is already in place, adding a new app to the same device simply updates the device entry.

In this case - and I am speculating - I wouldn't expect the existing Bible! app to be added to any device entry which is created.

Donnie Hale

https://community.logos.com/discussion/comment/650600#Comment_650600

In this case - and I am speculating - I wouldn't expect the existing Bible! app to be added to any device entry which is created.

In that case, it seems like I ought to just uninstall and reinstall the Bible! app itself. <sigh>

Thanks again,

Donnie

Russ White

My wife and I are having similar problems.

1. Every time you open the app, it says there are books that aren't downloaded and should be. Hit "okay," go into the app. Some books can't be opened (ones that should be downloaded). Happens every time you open the app.

2. Touch screen over point where you should be able to enter a reference, nothing happens.

3. Commentaries aren't sync'ing correctly to the Bible text (for those commentaries that actually work).

My wife has stopped using the app because it's unstable and problematic on her brand new ipad air 2... It's not extremely useful on my new ipad mini retina, either. Seems like the app has a lot of problems, probably needs to be looked at.

Russ

Into Grace

https://community.logos.com/discussion/comment/651011#Comment_651011

I sure hope Logos starts fixing this app. I reset my password a week or two ago and lost gigs of resources that were deleted. Most users (in my opinion) spend far more time using hand held devices than the desktop application.

Logos, please take pride in your company and give your customers an improved IOS/Android experience.

Ken Brown

I am having the exact same issues you relate.

Ken Brown

I also just updated to a iPad Air 2 with 128 gig. The app is completely unusable to me. I am unable to open any resources or use them. I can force the homepage to open, but it locks up and will not let me do anything. Everything you relate are the exact same issues I am having. I was not having these issues on my previous iPad with 8.1, but on this one, yes. If I hit cancel the download, it hangs. If I say yes, it hangs. If I am in the homepage, it hangs. The app hangs and will not allow you do anything. 4.3.7 is incredibly useless whereas the previous tool iteration was useful. Vyrso seems to be working. Faithlife seems to be working. But Logos, not so much.

John Goodman

https://community.logos.com/discussion/comment/651654#Comment_651654

I was having this issue after update and did two things to solve it. One was that my ipad memory was full. This may not apply to you. The other thing I did was to remove Bible! and install it again. Ok it took hours to sync back up but works again now.

Ken Brown

https://community.logos.com/discussion/comment/651670#Comment_651670

Mine was a complete new install to begin with. I may give that a go, couldn't be worse than what I have right now.

Ken Brown

https://community.logos.com/discussion/comment/651696#Comment_651696

That seems to help. Thanks

JT (alabama24)

https://community.logos.com/discussion/comment/651703#Comment_651703

That seems to help. Thanks

Are you up and running now? Good to go?

Question: Did you previously have many downloaded resources? How many do you have now? How much space is the app taking up on your device? Is the sync completely finished now?

Donnie Hale

https://community.logos.com/discussion/comment/651789#Comment_651789

Things seem to be working for me now. It did take an uninstall / re-install of the Bible! app to get things into a usable state.

Here's a *possible* sequence to follow to get things improved:

- Uninstall the app
- Remove the device (all versions of it) from your "Manage Accounts" - Devices page
- Make sure the device no longer appears in your desktop Logos "Library" view
- Re-install the app
- Make sure the device shows up again in Manage Accounts and Library

This is draconian, to be sure, because all of your downloaded resources are lost.

My $.02 ...

Donnie

Dave Dunkin (Logos)

https://community.logos.com/discussion/comment/652041#Comment_652041

If you who are having problems could send us your logs via Send Support Info, that will help us find the issue here. You can send them to ddunkin@faithlife.com. If you've already reinstalled, the info we need won't be in the log, unfortunately.

Donnie Hale

https://community.logos.com/discussion/comment/652367#Comment_652367

send us your logs via Send Support Info

Dave,

Unless the "Send Support Info" feature has been enhanced since I last tried to use it, I can't use the feature to send you logs. The feature requires a standard email app configuration (e.g. SMTP/POP3 in the base iOS Mail app) in order to send the logs. I don't have such a configuration. All of my device emailing is done via the GMail app. I'm not aware of any way to get access to the log files to send them from GMail.

FYI...

Donnie

Ken Brown

https://community.logos.com/discussion/comment/651789#Comment_651789

I am up and running and syncing. I have been able to add additional resources as well. Thanks.

Xegesis

I had the same problem when I got my Air 2. I just deleted the app and re-installed it. The resources downloaded with no problem after that and I haven't had a problem since.