Since the NIV84 resource said it was updated I get navigation failed errors. Uninstalling the resource and reinstalling fixes for a bit, but then starts again. No issue in other resources.
Frank
I think that this is down to a problem with the updated resource which affects, not only Android users but iPad/iPhone/iPod users as well. [:(]
See this link: http://community.logos.com/forums/t/71175.aspx
Hopefully, Logos will sort this out ASAP.
Every blessing
Alan
I've responded below, we're looking into it. Thanks for the report!
http://community.logos.com/forums/p/71175/496351.aspx#496351
In the interim could the previous version be made available to download? While I can get around the error by deleting the downloaded version and using it through the cloud online, I don't always have access to wifi so no access to my primary Bible.
Has there been any update on this issue? Very annoying to have restricted capabilities with your preferred Bible.
This is also the perfect example of why the user needs the ability to turn off automatic updates. I could go back to my backup but the app auto updates
Has there been any update on this issue?
Yes - if the NIV84 it's downloaded locally, please remove it and download it again. That should fix the problem.
Has there been any update on this issue? Yes - if the NIV84 it's downloaded locally, please remove it and download it again. That should fix the problem.
Thanks Kevin, I'll try again later to download. Right now it comes up with an error that it failed. Tried removing the resource and a fresh install with clearing of the app data as well with no fix.
Update: I have no problem downloading other resources, but I only get the download failed error for the NIV84 on both my phone and tablet. On both I have removed the resource and have uninstalled the API with no change.
The issue is fixed for iOS and Windows RT, but Android is a little more strict about how the "fixed" resource was bundled. We have corrected the NIV84 internally and intend to update the servers soon.
Latest fix has things back to normal. Thanks Kevin
I'm glad it's working again - Cheers!
