Reference could not be located issue
Ever since the version 4.6.3 update, I haven't been able to use the Exegetical and Passage Guides.
All I get is error message:
"Reference could not be located issue".
It renders my most used function in Logos useless.
What should I do to solve this issuse?
Comments
-
-
Just checked all my guides. They work. FYI. On latest app.
0 -
I use it every day without any problems, and haven't changed any thing, except letting Logos update it self.
My Logos is English and it has constant internet connection, both wifi and cellular.
App info
version: 4.6.3071
Display driver: 2015-03-06T00:00:00Z
0 -
-
The above screen shot is the only screen I get when I try to run the guides. It won't even allow me as far as to type any syntax.
0 -
Jan,
Please use the "Report a Problem" item in the Help panel so we can take a look at your device logs.
0 -
That's already done, Kevin.
0 -
I'm unable to reproduce this issue, but your logs did seem in indicate you had cancelled resource downloads. How many resources do you have downloaded locally and did you happen to cancel that process?
When you installed 4.6.3 was it a fresh install or an upgrade?
0 -
I have 3558 resources downloaded. I haven't cancelled any downloads, but there are a few resources that won't download; but that has never affected the use of the app.
The installation was an update through the AppStore.
0 -
I tried to delete and reinstall the app, and download the whole library again.
It didn't change anything - I still get same error.
I I did a new report on the error in the app.
Can any one help me?
0 -
Jan,
What language is your device set to use - English?
0 -
Jan,
I saw your Customer Service report - we need to know what language your device is set to use. Is your device set to English or something else?
0 -
My iPhone 6 plus is set to Danish, and my Logos is set to English.
0 -
My iPhone 6 plus is set to Danish, and my Logos is set to English.
As you surmised, it appears that something in the apps changed in how Guide references are resolved and/or how they are added to the History stack, we're not yet exactly sure. The only workaround I can find at the moment is to change your iPhone to English.
I will write up a case for the dev team, sorry about the issue.
0 -
Hi Kevin :-)
Would you have any further information on how it's going at the dev team?
0 -
Hi Jan,
The issue hasn't yet been fixed but I'll mention it again to them.
0 -
Hi Kevin
I am Jonghyun from Korea.
I have same problem. Though, when I change to english language, It works well.
0 -
Hi Jonghyun,
Thank you for reporting this. There are two issues here - one small, and one quite large.
1) Before version 4.6.3, Jan didn't see any problems using the Exegetical or Passage Guides when his iOS device was set to a Danish locale (Jan, please correct me if needed). After installing 4.6.3, Jan reported the problem. This is the first (small) issue, because Danish was formerly supported in this particular case and we should be able to fix it without much effort.
2) The second issue is supporting the Exegetical and Passage Guides in Korean (or Chinese, Japanese, etc.) - to my knowledge this has not yet been supported. We are working on adding additional language support.0 -
No need for correction - you got it right, Kevin :-)
Sounds good: "fix it without much effort" - soooo, a solution is coming soon? ;-)0 -
No need for correction - you got it right, Kevin :-)
Sounds good: "fix it without much effort" - soooo, a solution is coming soon? ;-)Oh dear...! I discussed this one today with James and we know it used to be an issue but then was fixed - but it came back. Software seems so easy but it's really not. I might have misspoke but please know that we are very aware of this issue as more languages are being added to our apps.
0 -
Dear friends at Faithlife/Logos :-)
Any news on this issue?
I'm currently running version 4.6.46101, but have not seen any fix to the problem, so fare.
It's kind of painstaking, because I can't use the Passage or Exegetical Guide - and I really, really need them!
Please let me know how fare you have come in solving the issue.
Thanks for all your great work for the Lord! :-)
Yours in Christ
Jan :-)
0 -
Hi Jan,
I just asked the dev team about this issue - a case already exists but it is not yet resolved. This issue happened once before so we hope to get a fix in with the next release.
0 -
Thanks Kevin :-)
I'm sorry to keep on bothering your guys with this issue - please forgive me.
Jan
0 -
Hi Kevin
I am Stanislav from Czech republic.
I have same problem. Does not work Passage Guide or Exegetical Guide, both exclusively from Genesis to the book of Leviticus but not in other books.
Though, when I change to english language, It works well.
0 -
Correcting:Passage Guide does not work or Exegetical Guide only from Genesis to the book of Leviticus, but not in other books.
0 -
Exactly the same problem. iOS 9,1 set to Czech UI, Logos 5.0.1 English. Yes, this issue was there about 1 or 2 years ago.
0 -
We are aware of this issue and apologize that it is not yet fixed.
0 -
Today update to 5.0.2. and the problem remains. [:'(]
0 -
Dear friends at Faithlife/Logos
July 10 2015 I made Faithlife aware of this problem, and since then several others from non-English countries has reported the same problem.
The problem arose with the 4.6.3071 version of Logos, and now I’m using the 5.1.30022 version, and the problem still remain.
8 months is a VERY long time to wait, taking in consideration that I/we actually pay for this function to work in the app.
I’m not trying to be offending, but my patience is tested here, dear friends.
Could you PLEASE make this a priority?
Sincerely Yours
Pastor Jan
0 -
Hi Jan,
This issue sort of dropped off the map so I'm glad you posted again. We had a couple of cases already but they hadn't been prioritized.
We believe this issue can be fixed on the server side without having to install a new version of the apps. The tentative plan is to deploy the fix sometime tomorrow, if possible.
I will report back on this thread once the deployment is complete. Thank you for being so patient and we apologize for taking so long.
0
