Text Comparison Issue
Has anybody else experienced problems with Text Comparison where when you select one of the translations for the verse you are comparing the app goes to the first verse of the chapter instead of the actual verse you are comparing? I thought it was resolved when I deleted the app from my iPad and re-installed it but the problem came back again. Then I decided to check my iPod Touch and the problem occurs on that also.
Comments
-
Hi Kerwin - and welcome to the forums.
I hadn't noticed this problem before but - having just tried it - I can confirm it!
I've just tried it on Android and there it takes you to the verse being compared so it looks like an iOS-specific issue.
Hopefully someone will be able to pick this up and look at it.
Graham
0 -
-
Hi Alabama
From what has been posted, looks as though v3 is going to be quite something!
Looking forward to it
Graham
0 -
-
Thanks Graham. Glad to know I wasn't the only one having the issue (from a getting this resolved perspective [:)]). Glad to know a fix was already in the works. Can't wait to see the new app. Even without the features we all can't wait to get this is still the best one out there (and I own quite a few). Hopefully more features will be available offline so my phone battery will last a little longer during the day. [;)][;)]
0 -
Looks like this issue still isn't fixed. Deleting everything and re-downloading doesn't even fix the problem. The issue can't be my iPad because no other apps have weird problems. Also, I have the same problem on my iPod touch. Everything works correctly on my android phone.
0 -
Looks like this issue still isn't fixed. Deleting everything and re-downloading doesn't even fix the problem
Can you restate the problem and provide screen shots? You can take pictures by pressing both physical buttons on the device. The photos are saved in your photos app.
Nevermind… I re-read your OP. I assume there is a regression here somewhere unless you are saying you have gone nearly a year without it working properly?0 -
-
It used to fix itself if I deleted and then re-downloaded everything. Then even that stopped working, but since nobody else seemed to have the problem I figured it wasn't going to get fixed because it wasn't a widespread problem. But then the problem showed up on my brand new iPod Touch. Now I know it's definitely not a "my iPad" problem. I figured it was time to bring this up again as now it can't just be a "one person's iPad" thing. It may be a "my" issue but at least I know it's not the equipment [:)]
0 -
-
Kerwin - I did get in touch with Logos in the beta forum and a case has been created. Hopefully it will be tracked down soon.
Thanks for the assist.
0 -
Just to make things more interesting, I have 2 translations that actually work correctly. I have 3 collections available.
In "Top Five" I have: KJV 1900, NLT, LEB, ISV, AMP. AMP goes to the correct verse while the other translations go to the 1st verse in the chapter.
In "Bible Collection" I have: DARBY, AMP, CEB, CJB. AMP goes to the correct verse while the other translations go to the 1st verse in the chapter.
In a collection I made up called "My Five" I have: AMP, EXPNT, KJV 1900, NET, NLT. AMP and NET go to the correct verse while the other translations go to the 1st verse in the chapter.
Hopefully this additional information can be of help to the developers.
0 -
Just to make things more interesting, I have 2 translations that actually work correctly. I have 3 collections available.
In "Top Five" I have: KJV 1900, NLT, LEB, ISV, AMP. AMP goes to the correct verse while the other translations go to the 1st verse in the chapter.
In "Bible Collection" I have: DARBY, AMP, CEB, CJB. AMP goes to the correct verse while the other translations go to the 1st verse in the chapter.
In a collection I made up called "My Five" I have: AMP, EXPNT, KJV 1900, NET, NLT. AMP and NET go to the correct verse while the other translations go to the 1st verse in the chapter.
Hopefully this additional information can be of help to the developers.
Any update on this situation? My text comparison still jumps to the first verse of the chapter in the NASB and ESB, but goes to the correct verse in NIV84 and NET. Interesting!
0 -
Unfortunately I've pretty much given up since I can't get anybody at Logos to seriously look at it. I can never get tech support to go past "delete the app, restart your device" even though it doesn't resolve the problem. The last rep I talked to said that's how it's supposed to work even though I mentioned that it works "properly" on my Android phone and a couple of translations on my iOS devices. Nobody can seem to understand that it can't be my iOS devices when it happens on 2 iPod touches and 2 IPads (including a brand new iPad Air). How can 4 devices be "broken" exactly the same way for one only app? Why can my Android phone get it right but not one of my 4 iOS devices (except for a couple of translations). Guess I'll never know until it breaks for somebody that works at Logos since not enough users seem to have the problem for the issue to be handed over to an actual developer to look at what could be possibly be causing the problem.
But I also understand the nature of business that if you have to prioritize the limited resources you have and have them focused on things that affect the many.
0 -
Kerwin .... it's probably because you didn't follow the rules:
1. Post the problem in the correct forum. If you're having a problem with an iOS Logos software then it should be posted in this forum.
2. Hopefully someone with a 'star' will answer and advice you on the correct procedure to do next. I notice two. One said re-post. So you should have done that (like you did).
3. Describe in excruciating detail the problem, so that just about no one can say the problem doesn't exist (except for Logos staff of course).
4. Be patient. One month at least. Let's see ... hmmm ... seven months. Well, you know, time flies.
5. Above all else, don't even hint there might be an issue at Logos. That brings out the Logos bees. Not pretty.
By the way I tried it, and indeed you're correct. But that's not actual evidence of a problem.
Actually that was the first time I tried Text Compare. It only gave me 5 Bibles. I'm a tagger, so that's all she could do. I'm hoping the iOS guys will take a look at the new Logos5 and how people can use 'tagging'.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Hi Kerwin
I have flagged it again to Logos, hopefully they will provide an update.
Graham
0 -
Kerwin .... it's probably because you didn't follow the rules:
1. Post the problem in the correct forum. If you're having a problem with an iOS Logos software then it should be posted in this forum.
I was simply responding to a question I was asked. If the iPhone/iPad forum is not the correct place to post about an iOS device issue with Logos I don't know what is. [:)]
2. Hopefully someone with a 'star' will answer and advice you on the correct procedure to do next. I notice two. One said re-post. So you should have done that (like you did).
I've actually spoken to tech support several times several times. Didn't see a need to re-post since I had talked to tech support on the phone with no resolution. Again, I only posted because somebody asked me a question.
3. Describe in excruciating detail the problem, so that just about no one can say the problem doesn't exist (except for Logos staff of course).
Explained problem in great detail with tech support on the phone as they followed along on their iPads, so never really had the need to post greater detail here.
4. Be patient. One month at least. Let's see ... hmmm ... seven months. Well, you know, time flies.
Gen 2 iPod Touch...iPad 2...Gen 5 iPod Touch...iPad Air...think I'll just get a Microsoft Surface Pro 2 so I can use the desktop version [;)]
5. Above all else, don't even hint there might be an issue at Logos. That brings out the Logos bees. Not pretty.
There's an issue? Why would you say there's an issue? LOL
Honestly I just let the issue go because I didn't feel like deleting the app and having to re-download all of my resources again. [:S]
By the way I tried it, and indeed you're correct. But that's not actual evidence of a problem.
Actually that was the first time I tried Text Compare. It only gave me 5 Bibles. I'm a tagger, so that's all she could do. I'm hoping the iOS guys will take a look at the new Logos5 and how people can use 'tagging'.
The last response I got pretty much was as you said--that how it works. Thing is that's not how it works on Android (at least a phone) or the desktop. Yes you only get 5 bible translations to compare where the desktop let you compare everything in the selected collection.
Again, I just simply had let it go because nobody else seemed to have the issue (or considered it a problem if they were having the issue) and only posted again because somebody asked me a question.
Did I mention that Logos Bible Software is a wonderful product?
0 -
Kerwin,
I'm very sorry no one ever got back to you on this issue. I'm not sure why it happened, but I'll do my best not to let it happen again. [:)]
In "Bible Collection" I have: DARBY, AMP, CEB, CJB. AMP goes to the correct verse while the other translations go to the 1st verse in the chapter.
I was able to reproduce the issue with this collection, just like you said. I'll write up a bug report and see if we can figure out what's causing the problem.
Thanks for your patience, and again, I'm sorry you've had to wait so long on this.
0 -
Okay, quick update: I was able to track down WHY the bug is happening, but I'm not sure who needs to fix the issue, iOS or the server team (I'm leaning towards iOS, since Android behaves correctly). I'm going to consult with James on Monday and see what he thinks.
0 -
Hi Drew
Thanks for the updates
Appreciated, Graham
0 -
Not a problem. Thanks for your help Drew.
0 -
James just checked in a fix for this bug. I don't think it will make it into the next release since the next release is almost out the door, but it will be in the release after that. Thanks again for your patience.
0 -
James just checked in a fix for this bug. I don't think it will make it into the next release since the next release is almost out the door, but it will be in the release after that. Thanks again for your patience.
Thanks Drew
That will be really helpful
Graham
0
