BUG: Logos Mobile word select produces nonsense
I've encountered this ever since I started using the mobile app back in May, but I only just figured out how to take a screenshot. This kind of result happens all the time.
Obviously, this is not the correct result for the highlighted word "see". Please fix this problem.
ASUS ProArt x570s Creator, AMD R9 5950x, HyperX 64gb 3600 RAM, ASUS Strix RTX 2080 ti
"The Unbelievable Work...believe it or not." Little children...Biblical prophecy is not Christianity's friend.
Comments
-
Three verses later, same erroneous result.
ASUS ProArt x570s Creator, AMD R9 5950x, HyperX 64gb 3600 RAM, ASUS Strix RTX 2080 ti
"The Unbelievable Work...believe it or not." Little children...Biblical prophecy is not Christianity's friend.
0 -
I can see where (conceivably) the v3 example might result from the way NASB95 was originally tagged ... 'make' and 'see' were both handed a 7200, and then re-tagged to just 'see'. But v5 is another odd problem ... a right-click (desktop) of v3 can find 7200 in TDOT, but not the same 7200 in v5. I wonder ... NASB95 never seemed to recover from Libby to Logos.
BTW, in your prophetic-stance, do you distinguish meanings (Strongs 7200 vs 5027). Just curious, given Akkadian background linkage.
0 -
This is strange!
It's not a resource-specific issue - the same thing happens with NIV
It's not a straight-forward tagging issue - the lookup happens correctly on desktop.
It's not limited to a particular mobile platform - I believe David is using an Android device, I have checked on my iPad
So it looks like some strange issue within the mobile app itself
0 -
David, DMB, and Graham,
We have reproduced this problem in house, and we are opening a ticket so that it can be fixed in a future update.
Thank you for bringing this to our attention.
0 -
Thanks Joe
That's good to hear.
0
