Strange Bug with command "type:commentary"

If I go to the library and type "proverbs type:commentar" or "type:commentar proverbs," then all commentaries for proverbs will show; however, if I add the "y" to "commentary," such as type:commentary proverbs, then nothing shows. For some reason finishing the word negates the command.

I've tried the same search with several books of the Bible, and at least in the case of Acts, one volume, The Beginnings of Christianity, Part 1... will show with the "y" included, but nothing more.

I also tested with "type:c," type:co," type:com," etc..., and the command guesses from the "c" that the word will be "commentary" and pulls up all commentaries until you get to the "y" where the library returns 0 results.

I'm on IOS 13.3 and Logos Bible Study Tools 8.10.0.

Find more posts tagged with

Mobile App

Comments

Graham Criddle

I see the same thing Joseph.

One detail is that the type for most commentaries is technically "bible commentary" but the mobile app doesn't seem to handle that correctly at all - I wonder if that is related to what you are seeing (the desktop handles it correctly)

And congratuations on 2,000 posts[:)]

Joseph Turner

https://community.logos.com/discussion/comment/1083285#Comment_1083285

And congratuations on 2,000 posts

Thanks!

Todd Diehl (Logos)

https://community.logos.com/discussion/comment/1083289#Comment_1083289

Thanks for the report Joseph. One thing to be clear about, the library index/search technology is different between mobile and desktop, and even between iOS and Android (I guess that is clear based on the report, but just wanted to state that up front).

It looks like once you get to "type:commentary" it is looking for a more precise match in this case. Another workaround would be to use "type:commentary*". That being said, I think we can probably infer the wildcard to improve the search your are looking for here. I've opened a case and will see about getting this resolved in a future version.

Joseph Turner

https://community.logos.com/discussion/comment/1083715#Comment_1083715

Thanks for the report Joseph. One thing to be clear about, the library index/search technology is different between mobile and desktop, and even between iOS and Android (I guess that is clear based on the report, but just wanted to state that up front).

It looks like once you get to "type:commentary" it is looking for a more precise match in this case. Another workaround would be to use "type:commentary*". That being said, I think we can probably infer the wildcard to improve the search your are looking for here. I've opened a case and will see about getting this resolved in a future version.

Thanks for the explanation, Todd!