NIV84 errors
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.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
Comments
-
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
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
0 -
Alan Macgregor said:
See this link: http://community.logos.com/forums/t/71175.aspx
I've responded below, we're looking into it. Thanks for the report!
http://community.logos.com/forums/p/71175/496351.aspx#496351
0 -
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.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
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
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Frank Sauer said:
Has there been any update on this issue?
Not yet - we're still working on a fix.
Frank Sauer said: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
This issue is related to the resource itself, not the version of the application (which is why the issue also appears in Android and Windows RT). In any case, if automatic updates could be turned off and a problem arose, the first thing we would ask is "are your resources updated and are you running the latest version of the app?" Similar to every other software company, we can't support millions of possible scenarios should users selectively decide to turn off updates. I hope you understand.
0 -
Kevin Byford said:Frank Sauer said:
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
This issue is related to the resource itself, not the version of the application (which is why the issue also appears in Android and Windows RT). In any case, if automatic updates could be turned off and a problem arose, the first thing we would ask is "are your resources updated and are you running the latest version of the app?" Similar to every other software company, we can't support millions of possible scenarios should users selectively decide to turn off updates. I hope you understand.
I'm glad you are still working on it, however please do not patronize me with the "Similar to every other software company"excuse. Microsoft, Google with Android and any other software I use has a way for the user to decide whether they want auto updates of the OS and Apps. I also fully understood that the issue was with the app itself and not the apk, which is why I mentioned going back to a backup I had not making a difference because Logos would force the update whether I wanted it or not.
You can try to explain it away in what ever misleading way you choose, Bob could attempt to do the same, however the point still does remain that this is indeed the perfect example of what I and many others were warning about with forced resource updates and not having the choice to opt out. If I had the choice as with any other software I would keep it disabled and would have not updated after the first report of the current issue. However Logos for the sake of limiting tech support phone calls has allowed any users that consistently use the NIV84 to be hindered across mobile platforms from doing so with efficiency for the sake of saving time on the support side.
In the future please do not try to mislead anyone with your outright deception in even hinting toward this being the policy of every other software company because it does not cast a good image on Logos as a company.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Frank Sauer said:
however please do not patronize me
Frank,
My intent was not to patronize you.
Frank Sauer said:You can try to explain it away in what ever misleading way you choose, Bob could attempt to do the same, however the point still does remain that this is indeed the perfect example of what I and many others were warning about with forced resource updates and not having the choice to opt out.
At this point I am not sure how to respond to this. I am not trying to explain anything away or be misleading.
Frank Sauer said:However Logos for the sake of limiting tech support phone calls has allowed any users that consistently use the NIV84 to be hindered across mobile platforms from doing so with efficiency for the sake of saving time on the support side.
Again - if you feel this way I apologize. It is not Logos' intent to hinder NIV84 users.
Frank Sauer said:In the future please do not try to mislead anyone with your outright deception in even hinting toward this being the policy of every other software company because it does not cast a good image on Logos as a company.
I apologize - I should have said "similar to many software companies." My intent was not to mislead or be outright deceptive.
It seems that we really must have started off on the wrong foot; I am on your side and just a few minutes ago asked again about the status of the NIV84 fix.
I don't know the history of you and many others warning Logos about forced resource updates; that decision was not mine to make and I might not have even been with the company at that time.
Please accept my apology. I will escalate the NIV84 issue again with the dev team.
0 -
Kevin Byford said:Frank Sauer said:
however please do not patronize me
Frank,
My intent was not to patronize you.
Frank Sauer said:You can try to explain it away in what ever misleading way you choose, Bob could attempt to do the same, however the point still does remain that this is indeed the perfect example of what I and many others were warning about with forced resource updates and not having the choice to opt out.
At this point I am not sure how to respond to this. I am not trying to explain anything away or be misleading.
Frank Sauer said:However Logos for the sake of limiting tech support phone calls has allowed any users that consistently use the NIV84 to be hindered across mobile platforms from doing so with efficiency for the sake of saving time on the support side.
Again - if you feel this way I apologize. It is not Logos' intent to hinder NIV84 users.
Frank Sauer said:In the future please do not try to mislead anyone with your outright deception in even hinting toward this being the policy of every other software company because it does not cast a good image on Logos as a company.
I apologize - I should have said "similar to many software companies." My intent was not to mislead or be outright deceptive.
It seems that we really must have started off on the wrong foot; I am on your side and just a few minutes ago asked again about the status of the NIV84 fix.
I don't know the history of you and many others warning Logos about forced resource updates; that decision was not mine to make and I might not have even been with the company at that time.
Please accept my apology. I will escalate the NIV84 issue again with the dev team.
No problem Kevin and I do appreciate your looking into the situation again. My response was to many similar statements which are not accurate in the majority of cases. In fact I personally cannot identify one software company that forces updates on its users. I do not use Apple products so maybe that is where these statements come from... However even in the most detrimental security flaws with Microsoft you have to allow the update unless you chose to have automatic updates. Any that have to do with resources like Office, Bing or in Windows 8 any of the apps you again have to choose to install unless set to auto update if available. Same with Android whether through the carriers sending an OTA update to the OS, using a AOSP OS like CM or Evervolv, apps from the Play store - all must be manually updated or allowing the update unless you choose auto updates.
So way back during beta testing days when Logos was going to the cloud many of us were complaining, beating the dead horse and warning that this is the main issue with not allowing users the right to opt out of auto updates, whether the PC version, Mac version or mobile versions. When we mentioned it, as with the data mining the "similar to every other software company" excuse was used and the fact that most if not all of them allow the opt out of auto updates and data mining was ignored.
So again thank you for escalating this issue but please be aware that statements like those I responded to are very inaccurate and deceiving to the end users.
Thank You
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Frank Sauer said:
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.
0 -
Kevin Byford said:Frank Sauer said:
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.
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Frank Sauer said:
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.
0 -
Latest fix has things back to normal. Thanks Kevin
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Frank Sauer said:
Latest fix has things back to normal. Thanks Kevin
I'm glad it's working again - Cheers!
0
