Mobile Search is flaky and often fails
Phrase searching on a mobile device is flaky and often doesn't return results for text that I know exists. For example, yesterday I wanted to look up a hymn, so I ran this search:
It sat then spinning for several seconds, and returned no results.
Then I immediately retried the search, and got the hits I expected:
I used to think it was overloaded servers on Sunday, since that's when I use the mobile search the most. But just now (on Monday evening) I was able to duplicate the failure using the same search phrase. It seems to be limited to phrase searching with quotes, probably because that's the slowest kind of search.
I hope this can be fixed, as this has been occurring for months and is rather annoying. At least return an error message instead of "No results", because it's misleading.
MacBook Pro (2019), ThinkPad E540
Comments
-
Please use Report a Problem under the Help menu so we can take a look at the app logs - also include this thread in the email.
If possible, please don't wait months before reporting problems as this might have been fixed months ago (if we had known about it).
0 -
Please use Report a Problem under the Help menu so we can take a look at the app logs - also include this thread in the email.
I sent the Report a Problem email. I was able to reproduce the problem using a different search phrase before I sent the email ("sometimes a hymn brings back memories") because the phrase in the original post was not currently doing it.
If possible, please don't wait months before reporting problems as this might have been fixed months ago (if we had known about it).
I reported it two months ago on the Faithlife Mobile Apps Beta group: https://faithlife.com/posts/706539
I don't like to report problems I experience when using the beta in this forum. But now, since I'm currently not on the beta, I figured I'd get better visibility for this problem here, so I'm reporting it again.
MacBook Pro (2019), ThinkPad E540
0 -
Thanks Todd,
Sorry for missing your earlier post in the Beta group. For some reason we didn't get your app logs but we might not need them now - the server team is looking into ways to make search more performant. I'll let you know when the changes are deployed.
0 -
Hi Todd,
Please try these searches again and let us know if there are any performance improvements.
0 -
Please try these searches again and let us know if there are any performance improvements.
I found that the search failures no longer seems to happen. It looks like the timeout value was raised. This is good news.
On the other hand, performance is not what I would call responsive. A search for "hound of heaven" took 10 seconds, while a search for "wonderful grace of Jesus" took 25 seconds. That's a long time, but each search did finish and returned hits, and for that I'm grateful.
Searches do seemed to be cached, as subsequent searches of the each phrase returned immediately.
MacBook Pro (2019), ThinkPad E540
0 -
I have an iPad 2. I wanted to do a Bible search in the NT for 'depraved'. I selected NT for search range and it came back with passages from the OT.
Also, sometimes I have to reboot my iPad to enable a new search.
Any thoughts?
0 -
I have an iPad 2. I wanted to do a Bible search in the NT for 'depraved'. I selected NT for search range and it came back with passages from the OT.
This is a known issue caused by a recent server side change; we hope to have a fix in the next day or two.
Also, sometimes I have to reboot my iPad to enable a new search.
Please create a new post - also see https://community.logos.com/forums/t/118697.aspx .
0 -
I have an iPad 2. I wanted to do a Bible search in the NT for 'depraved'. I selected NT for search range and it came back with passages from the OT.
Was this still happening when you posted (at 4:57 PM PST)? It should have been fixed about four hours before your post (approx 12:30 PM PST).
0 -
I have an iPad 2. I wanted to do a Bible search in the NT for 'depraved'. I selected NT for search range and it came back with passages from the OT.
Was this still happening when you posted (at 4:57 PM PST)? It should have been fixed about four hours before your post (approx 12:30 PM PST).
I just verified that reference/passage ranges now work as expected. Joe, please let us know if this issue is corrected for you as well.
0 -
Range search works now.
Thanks
0
