BUG/Frustration - Logos Bible AND Faithlife Ebooks forgets where you are in Bibles (Android 6.3.1 Build 603015171)

Page 1 of 1 (7 items)
This post has 6 Replies | 2 Followers

Posts 856
Tim Hensler | Forum Activity | Posted: Thu, May 3 2018 7:45 AM

When reading through the Bible, App version 5 would remember where I was the next time I launched the app.  Since version 6, the app doesn't remember - I'll close my tablet or the app at Luke 22, but the next time I open the app it will resume in Luke 21.  The gap between where I was and where it opens can be one or two chapters behind and other times it is many chapters behind where I left off.

The same thing happens when I have a couple tabs populated (a Bible, study Bible notes and a commentary).  Whether they are linked or not, if I swipe from the Bible to view one of the other books, and then swipe back to the Bible, the Bible usually isn't where I left it.

Linking books together gets very messy because the app usually forgets where it was in one or more of the books, so I don't link books (though I really would like to).

This happens with both the Logos Bible and Faithlife Ebooks Apps.

My wife has her own tablet, the same model tablet I have (Samsung Galaxy Tab A; SM-T580), and she has the same problem.  I read from NASB on my tablet and she reads from NKJV with MacArthur Study Bible in the lower part of a split screen on hers.

Posts 144
Josiah | Forum Activity | Replied: Thu, May 3 2018 8:44 AM

Same problem on Android.  Very frustrating.  I have stopped reading on my phone and I used to read quite a bit.  It was perfect in Version 5.  Now the only option is to intentionally open a second tab of the same resource before closing OR never close the app.  I don't like either of those options.

Posts 144
Josiah | Forum Activity | Replied: Thu, May 3 2018 8:46 AM

Also for me it's pretty much every resource.  I tend to read expository/application type commentaries straight through on my phone but it's impossible now always jumping 20 pages or so backwards each time I reopen the app.

Posts 856
Tim Hensler | Forum Activity | Replied: Tue, May 8 2018 7:47 AM

Faithlife - Have you looked at this yet?  Have you duplicated the problem?  Has a case been opened?  

Not hearing a response from Faithlife on bug reports is discouraging to those of us who are beta testing for you.  This is one of several bugs reported on this forum with little or no response from Faithlife.  The Logos 7 beta form (https://community.logos.com/forums/141.aspx) is very interactive  - helpful to Faithlife, encouraging to beta testers and beneficial to all users of the application.  

The tweaks and small features/functions reported in recent Beta Release Notes on the Mobile Reader Apps (Beta) forum are nice, and I am sure there is a long list of more to add, but there needs to be a priority on performance and stability issues - add the additional features/functions once you have the existing ones working properly.  Your customers will thank you.

Posts 279
LogosEmployee
Daniel Di Bartolo | Forum Activity | Replied: Tue, May 8 2018 9:23 AM

Tim Hensler:
Faithlife - Have you looked at this yet?  Have you duplicated the problem?  Has a case been opened? 

Hi Tim, 

We've opened a case on this issue and we're actively working on it. I'm sorry that it has taken so long for you to get a response. 

You can always email me at danieldibartolo@faithlife.com if you aren't having any luck here. I'm happy to help. 

Thanks,

-Daniel Di Bartolo

Mobile Product Manager

Posts 856
Tim Hensler | Forum Activity | Replied: Tue, May 8 2018 9:35 AM

Thank you, Daniel, for your update on this issue and also your permission to contact you if the forum is not responsive.

Posts 856
Tim Hensler | Forum Activity | Replied: Sat, Jul 7 2018 7:42 PM

Daniel Di Bartolo,

It's been 2 months since this was reported, the Logos Bible App and the Faithlife eBook App on my tablet are up to version 6.5.1 (Build 605011191) and this problem still exists.  This is more than inconvenient - it is impacts my study and teaching process.  What is the status?  When can we expect a resolution?

Page 1 of 1 (7 items) | RSS