navigation failed on niv84

I'm having 'navigation failed' come up when trying to use book/chapter/verse selector in niv84 version of Bible. It only happens when I have downloaded the resource -it doesn't happen when I have removed it and am accessing the resource online.

I've tried downloading the latest version of niv84 -but the same thing happens.

I'm using Logos for android version 2.5.3.3. (Build 125)

Android version 4.1.2 on Samsung galaxy note 8.

I've seen previous thread - but solution on there doesn't solve problem.

Any help gratefully received as this fault is frustrating.

Find more posts tagged with

Mobile App

Comments

Frank Sauer

Phil,

This has happened before and we had to wait on Logos to implement and upload a fixed resource. http://community.logos.com/forums/t/71175.aspx?PageIndex=1

I'm also having the same issue and hope Logos moves quickly. Not good when a bad resource gets out on the weekend with Sunday services and studies....

steve clark

https://community.logos.com/discussion/comment/530714#Comment_530714

happened to me this morning. It stuck on Exodus. Finally tried turning off Notes and manually paging to the next book. Then shut down the app and powered down. Then when i powered up it would let me change to a NT book that we are studying at church tonight.

It was really weird. No matter what i tried it remained in Exodus. Even tried shutting down the app, changing Bible translations. But the NIV84 stayed stuck on Exodus until what i tried above. Fortunately i had Vyrso and Faithlife apps which allowed other translations (as that is why i use them, so i can quickly jump to multiple translations when studying).

Sean

https://community.logos.com/discussion/comment/530721#Comment_530721

I have the same problem, however, navigating through the table of contents rather than the book/chapter/verse selector works.

Frank Sauer

https://community.logos.com/discussion/comment/530732#Comment_530732

bump for Team Logos review.

Kevin Byford (Faithlife)

I'm having 'navigation failed' come up when trying to use book/chapter/verse selector in niv84 version of Bible.

Phil,

I've reproduced this and will write up a case. It's a book bug and happens on both iOS and Android.

Drew Hannay

I'm using Logos for android version 2.5.3.3. (Build 125)

Phil,

As Kevin mentioned, this is a bug with the resource which means it will be fixed on the server and shouldn't require an app update, but out of curiosity, is there any reason why you are running Logos 2.5.3.3 instead of the latest version (2.6.6)? Typically if you're having an issue the first thing to do is check for an app update. [:)]

Phil Michell

https://community.logos.com/discussion/comment/530927#Comment_530927

Thanks for the advice. I've updated to the latest version, deleted the resource, then re-downloaded it - but am still getting the same message. Hopefully Logos will sort it soon. Will watch this space.....

Kevin Byford (Faithlife)

https://community.logos.com/discussion/comment/530969#Comment_530969

Thanks for the advice. I've updated to the latest version, deleted the resource, then re-downloaded it - but am still getting the same message. Hopefully Logos will sort it soon. Will watch this space.....

Drew is correct, we always want customers to run the latest stable versions of the app since there's always a possibility the issue at hand has already been fixed. In this case the NIV84 resource bug is unrelated to the version of Logos you are running.

I'll update this thread when a working NIV84 is available.

Kevin Byford (Faithlife)

https://community.logos.com/discussion/comment/530981#Comment_530981

I'll update this thread when a working NIV84 is available.

The NIV84 resource has been fixed - please remove/download the resource again for offline usage.

Phil Michell

https://community.logos.com/discussion/comment/531017#Comment_531017

Hi Kevin,

I've reinstalled niv84 -and it now works fine.

Many thanks for your help.

Phil

steve clark

https://community.logos.com/discussion/comment/531076#Comment_531076

Re-downloaded the NIV84 and now it is working fine. Thanks Logos!

Michael Teegarden

https://community.logos.com/discussion/comment/531017#Comment_531017

I received the new version of the app today and thought that might clear up this issue, but it is still not navigating even after I deleted and re-downloaded the NIV84. Any other suggestions?

Frank Sauer

https://community.logos.com/discussion/comment/531398#Comment_531398

Just had an NIV update today and back to navigation failed. Removed and redownloaded to no avail still getting the failure message.

Kevin Byford (Faithlife)

https://community.logos.com/discussion/comment/531398#Comment_531398

I received the new version of the app today and thought that might clear up this issue, but it is still not navigating even after I deleted and re-downloaded the NIV84. Any other suggestions?

It appears that this issue somehow crept back, we're in the process of fixing it.

Kevin Byford (Faithlife)

https://community.logos.com/discussion/comment/531884#Comment_531884

I received the new version of the app today and thought that might clear up this issue, but it is still not navigating even after I deleted and re-downloaded the NIV84. Any other suggestions?

It appears that this issue somehow crept back, we're in the process of fixing it.

This is now fixed - please remove and download the resource again, and sorry this crept back.

Scott Sleeper

https://community.logos.com/discussion/comment/531900#Comment_531900

Seems to crept back in as I'm getting the navigation failed still after deleting and re downloading. Works fine when not using offline version. Thanks - Scott

Scott Sleeper

https://community.logos.com/discussion/comment/533230#Comment_533230

Interestingly, the NIV navigation works on my Galaxy note II but not on my Galaxy tab 3.

Kevin Byford (Faithlife)

https://community.logos.com/discussion/comment/533230#Comment_533230

Seems to crept back in as I'm getting the navigation failed still after deleting and re downloading. Works fine when not using offline version. Thanks - Scott

Hi Scott,

This is now fixed (again); please remove the resource and download the fixed version. We're working on a permanent solution so this won't happen again.