Bug: Reading plan navigation bar

Donnie Hale
Donnie Hale Member Posts: 2,036
edited November 21 in English Forum

Latest version of FL mobile app (8.02), iPad Pro 10.5, iOS 12.1

My reading for the day was in CSB, two passages - Psalm 119:1-24 and Titus 1:1 - 2:15. In previous versions of the app (pre-8 for sure), when there were multiple passages, there would be a gray navigation bar at the end of the first passage with a link that when touched would take me to the second passage. That bar didn't appear today. There was the gray bar before Psalm 119:1 (which had a link to the Titus passage in it - not very useful there), and there was the gray bar at the end of the Titus passage where I could touch "Mark complete." But not the other one as in the past.

I've seen flakiness in these bars for years now, though never the absence of an expected one when other expected ones are present. The most common problem is that they say "Yesterday" even though it should say "Today." I still see these kinds of problems, and the most reliable way to fix them is to go into View Settings for the resource, turn off the display of the reading plan, then turn it back on. At that point "Today" would be displayed.

Because of that long-time experience, I tried that with today's problem - disabled then re-enabled the reading plan in the CSB. That did not correct the problem. The expected bar after Psalm 119:24 never appeared.

FYI, and thanks.

Donnie

Tagged:

Comments

  • Donnie Hale
    Donnie Hale Member Posts: 2,036

    This is still happening. It's one of a number of bugs in reading plan behavior on mobile. This particular issue is with a reading plan I have for CSB. In the original post it was related to Psalm 119, and it is here as well.

    I've got a couple of screenshots to help demonstrate the issue. In the first one, you can see I'm at the end of Hebrews with a navigation bar that's supposed to take me to Psalm 119:72.

    In this second screenshot, you can see where I arrived when I tapped the link in the navigation bar at the end of Hebrews - the beginning of Psalm 119.

    As I see this again, it may be a resource issue. I'd appreciate a response from FL.

    Thanks,

    Donnie

  • Donnie Hale
    Donnie Hale Member Posts: 2,036

    I'd appreciate a reply from FL on this issue.

    Thanks,

    Donnie

  • George
    George Member Posts: 476 ✭✭

    I can confirm this.  It also occurs in ESV.  The NASB seems to be OK.

  • Daniel Di Bartolo
    Daniel Di Bartolo Member, Logos Employee Posts: 326

    It's possible that an out of date resource is causing this issue. Please try removing and then redownloading the resource and let me know if that helps. 

  • Donnie Hale
    Donnie Hale Member Posts: 2,036

    I know it's been a while since FL's reply. I tried redownloading the resource, but I still see the problem in various places.

    Here's the latest place where I've seen the problem. See the screenshots. Today's reading was Malachi 3-4 and then Psalm 141-142. If you look at the reading plan navigation bar in Malachi, you'll see that it's before Malachi 4 instead of after Malachi 4.

    So I think there's still some kind of problem, either with reading plans and/or with the CSB resource.

    Thanks,

    Donnie

  • GregW
    GregW Member Posts: 848 ✭✭

    I’m having the same issue on my iPad Air 2 and brand new iPhone XR, both on latest IOS version. It’s occurring with the 2011 NIV and NA28. I have a Custom Reading Plan for Psalms on the NIV, and a Reading Plan for the whole NT on NA28. App was only installed on the iPhone about 3 days ago So I’m reluctant to do a reinstall. I have removed the relevant resources from each device and re-downloaded. I have another Reading Plan for Institutes of the Christian Religion and reading markers are appearing correctly on both devices for that. 


    Running Logos 6 Platinum and Logos Now on Surface Pro 4, 8 GB RAM, 256GB SSD, i5

  • GregW
    GregW Member Posts: 848 ✭✭

    It’s now working for me - changing the view settings fixed it but I have no recollection of switching Reading Plans off in those two Bibles, but everything’s working again .


    Running Logos 6 Platinum and Logos Now on Surface Pro 4, 8 GB RAM, 256GB SSD, i5