Crash in reading list, when using non-mobile bible version

Logos app 4.0.8
Android 4.1.2
Galaxy S3

Opening reading a reading list crashes the app if that list is attached to a bible version that is not licensed (#$%@!!!) for mobile use. They do not show up on the home page, but they are accessible from the documents page.

Not being accessible is a problem, because it is confusing. It took me a while, and a lot of faulty attempts before I understood the problem. Having the app crash is obviously not much better, so something else is necessary. It would be best if the app could inform you of the problem and offer to display the text in a different bible version.

Find more posts tagged with

Comments

Graham Criddle

Hi Sakarias

Can you let me know which Bible you are trying this with?

I just tried it with a non-Bible resource which isn't mobile-enabled. As you say the reading plan document is visible in the documents menu but when I tried to open it, it reported that it couldn't open the document. It might have been better if it said that it couldn't open the resource but at least it didn't crash[:)]

Graham

Luigi Sam

It would be best if the app could inform you of the problem and offer to display the text in a different bible version.

better yet:

pop up with "do not display again, just flash red and goto default bible version"

that way: if there are heaps of these you dont get a pop up every time.

Sakarias Ingolfsson

https://community.logos.com/discussion/comment/545731#Comment_545731

I am using a norwegian bible called NT-05. Not only is it not available on mobile, it is no longer available for purchase to the desktop. It used to be in the SESB bundle

Second document from the top

Graham Criddle

https://community.logos.com/discussion/comment/546045#Comment_546045

Thanks for that.

I don't have that version so can't try and reproduce but hopefully this will help someone from Logos to track it down

Gabe Martin

https://community.logos.com/discussion/comment/546045#Comment_546045

Thanks for the report Sakarias. I've documented the issue and it should be be addressed in a future update.