Page 1 of 1 (13 items)

This post has
12
Replies |
2
Followers

It seems that ever since the iOS version 6.0.1 came out, the reading plans did not work correctly. This video (https://youtu.be/GXrvXtpZThY) demonstrates the same reading plan working correctly on macOS but not on iOS

I have shared a link to the video showing the behavior in my original post above, were you able to access it? The first portion of that video shows the reading plan as it works in macOS, and the second part shows the same reading plan as it performs within the iOS app.

I have also attached the zip file containing all the logs that was generated within the app.

I am at a loss as to what other details are needed, so please provide me with more specific details of what you need, and I will gladly oblige.

If you do not want to see visually what is actually happening and have a better background for finding and fixing the bug, then it’s your loss.

I made the effort to report and document the bug for you, and attached the log files as well to keep them together for you. If you choose to not make use of it, then so be it. I did this as unto the Lord Himself, and the rest is in His loving hands.

If you do not want to see visually what is actually happening and have a better background for finding and fixing the bug, then it’s your loss.

I don't work for FL, but I am always concerned to help make the apps better. I know that you took some time to make the video, but the best strategy is to make it clear up front. The video may be helpful to FL in the future, but it is more important to make sure you are understood first. Otherwise it will end up becoming TL;DR (or in this case, TL;DW).

Having looked at the video I think the problem you are describing is that a particular reading plan containing at least three Bible portions only displays links to the first two and not the third on iOS.

Is that correct?

Have you seen this behaviour on any other plans with multiple segments or just this one?

When I got home, I downloaded the Logos app on my iPad, and all of the reading plans work correctly, including the NIV, which I showed in the video. This indicates, to me at least, that something might have gotten corrupted in the library database somehow. One possibility is that I have over 1,300 resources in my library, and I downloaded them all onto the iPad. I have the large iPad Pro with 128GB RAM, and I like to have everything with me wherever I go. I wonder if the iPad app might not be fully equipped to handle that many resources.

Would you like me to wipe out the Verbum app altogether and see if a fresh install might be the ticket?

I wonder if the iPad app might not be fully equipped to handle that many resources.

The mobile app isnt designed to have so many downloaded resources. Corruptions are easy to happen.

Michael Sheaver:

Would you like me to wipe out the Verbum app altogether and see if a fresh install might be the ticket?

The best fix for many issues is a clean install. Since it is working properly with the Logos app, that may be what you have to do. I would try deleting the single resource from your iPad first, however.

Hi everyone! Please forgive me for not posting this earlier, but it seems that this behavior is a bug after all. This is what I received via email last week:

"Thank you for your reply. I have checked into this with my tech team and they’re letting me know there’s currently a known issue where Reading Plan markers sometimes don’t appear. We would recommend removing the reading plan and creating an identical one, then using Catch up to Today to get current readings."

In My case, the ios app does recognize my custom plan created in my imac IN the list of documents but it doesn't show the markers in my preferred bible. It only worked when I first downloaded the app. After that it never was the same.

In My case, the ios app does recognize my custom plan created in my imac IN the list of documents but it doesn't show the markers in my preferred bible. It only worked when I first downloaded the app. After that it never was the same.

It would be helpful if you could create a new thread and provide more details, including any steps taken to try and fix the problem.