Reference could not be located issue
Comments
-
Jan,
We have deployed a fix that we think should solve the issue for you, Pavel and Stanislav but possibly not for Jonghyun (yet).
If possible, please try again and let us know how the Exegetical Guide, Passage, Guide, etc. are working for you.
0 -
The problem still remains. I suspect it is related to the transfer of names of biblical books into the national languages. If I'm not mistaken, previously, were the names of biblical books in English. But I'm not sure now.
0 -
My experience matches that of Stanislav.
- The problem still remains: the Passage Guide and the Exegetical Guide keep saying: “Sorry, that reference could not be located – OK”
- I see that LOGOS now display the Biblical Books in my native tongue (Danish); but I don’t think that’s the problem, because the problem was around before that change.
A few comments on the use of guides in the Logos app.
- When using the Topic Guide, and you use the drop-down-menu in the upper right corner, you get the option to choose Books and Verses from the Bible.
But, that doesn’t make sense, since a Bible verse cannot be a Topic, only words can. - When using the Bible Word Study Guide, you rightly don’t get that drop-down-menu, as mentioned in the Topic Guide issue.
On the "Bible! vNext" app, 5.1.393 version, (TestFlight) the problem is there too.
0 -
Jan,
We thought we had this fixed but it isn't. I personally tested it but the test platform I used seemed to be at fault and I didn't test it completely... I apologize. I later tested it more thoroughly and realized the fix wasn't there.
I won't forget about this one again until it is fixed.
0 -
As for me, the issue persists. Both, iOS and Logos are of newest version, no beta installed, UI set to Czech.
BUT, After swithching iPd UI to English for teting purposes, the issue is GONE. But, understand me, I want to use iPad in my language. This workaround is not acceptable for me.
0 -
Hi Pavel
As for me, the issue persists. Both, iOS and Logos are of newest version, no beta installed, UI set to Czech.
BUT, After swithching iPd UI to English for teting purposes, the issue is GONE. But, understand me, I want to use iPad in my language. This workaround is not acceptable for me.
In Kevin's post above he acknowledged that the problem is still present - so it is recognised.
Graham
0 -
Kevin, sometimes I find myself serching for a "Like"-button [Y] on the forum - guess Facebook is shaping my world more than I like [;)]
Thanks for taking care of this issue - God bless you, dear brother in the Lord [:D]
0 -
As for me, the issue persists. Both, iOS and Logos are of newest version, no beta installed, UI set to Czech.
BUT, After swithching iPd UI to English for teting purposes, the issue is GONE. But, understand me, I want to use iPad in my language. This workaround is not acceptable for me.
Yes, we understand this is not a practical workaround and there is already a case to resolve this issue. We're still working on it.
0 -
Thank you, Kevin. My last post was considered as a feedback that the issue persists, not a complaint. [:)]
0 -
Finally! After a long wait, and after the last update of the Logos guides works again! Thanks for solving the problem! [Y]
Stanley
0 -
Thank you! After upgrading to 5.3 everything works fine. I hope this issue never happens again.
0 -
Hallelujah! [Y]
With the 5.2.00014 version update, the bugs are gone! Thanks [:)]
0
