Lexham English Bible Version 3

Hi Robert

It seems to be a verse pickers issue.

In the verse picker, mine only allows you to choose verses from the NT but if I move to "contents" I can get OT books as well.

Do you see the same?

Graham

Hi Graham, yes same thing here as well but when I click on the contents and go to a book in the Old Testament its blank.  This is for downloadable and online viewing in the IPAD IOS application for this particular bible.   Biblia.com works fine for both Old and New Testaments.

Redownloaded the bible.  I now see all the books in ot and new testament but verse and book chooser for ot not working.

Hi Robert

Thanks for confirming, looks like there is a problem with the resource.

Hopefully Logos will comment on this soon

Graham

Thanks Graham

The Android edition appears to be ok. Based on your avatar, you might prefer Young's Literal

Hi Robert

I have been looking at this further and the problem seems to be that the verse map isn't bring updated automatically.

Try removing the resource from your device, from within the library in the iPad app.

Then exit Logos and restart it.

Try and access the verse chooser in LEB without downloading the resource  again.

For me, this forced the verse map to be updated and I could them see books from both Testaments.

I then downloaded the resource again and it now all works.

There may be some simpler steps to follow but this worked for me.

So the problem is not in the resource but in the update / refresh mechanism.

Hope this works for you.

Graham

 

Yes, that also worked for me as well.  I had the old version downloaded and removing redownloading fixed it.

Excellent

Hi Robert

The Android edition appears to be ok.

And thanks for your response- it encouraged me to look at the problem more deeply!

Graham

Is anyone else having issues with the download of this bible into the IPAD?   Edition 3 has both the Old and New Testaments in the application but the IPAD version does not have the Old Testament.   Is this a licensing issue?

Hi Robert,

This isn't a licensing issue but appears to be something wrong with keylinking.  I've written up a case and forwarded it to our Development Department.  Thanks!