Reading Plan - Have to select it twice on the home screen - BUG?

Yes this is an issue that has been flagged before

You will find it opens directly from the homepage if the resource you are reading is not already open. If it is open you get what you describe.

I am hoping this will get fixed soon.

Thanks Graham!

This remains an issue with the latest update (6.0.7) on both the iPad Air 2 and iPhone 7.

This remains an issue following the latest update.

This issue has gotten worse in the 6.2.3.x and 6.2.4.x releases. Previously, the first touch of the plan on the home page would quickly flash to the CSB at the right location but then go back to the home page. The second touch would actually take you to the CSB. This assumes you were not already in the CSB when you navigated to the home page.

Now, when on the home page, you can press the reading plan as many times as you want. All it will do is go to the previously active resource and then go back to the home page. This is true even if the active resource is the CSB. At this point, this bug really needs some attention.

iPad Pro 10.5 128GB wifi, 11.2.5

Thanks,

Donnie

Now, when on the home page, you can press the reading plan as many times as you want. All it will do is go to the previously active resource and then go back to the home page. This is true even if the active resource is the CSB.

I am running beta, on my iPhone, and am seeing something similar... but not the same. 

When another tab is active, pressing the reading plan button simply dismisses the home page and shows the current tab. If the correct resource is in the open tab, it will take you to the right spot. NOTE: Due to another bug, I continue to have to rebuild my reading plan when the resource is updated. The description I gave is for a working reading plan. 

Donnie, same issue on my end. I just decided I was not going to continue to spend time on it in the forums as Logos seems to have a repeated quality control issue on this item. I have started to give the app 2 stars or less (highlighting the issue) and will continue to do so for each update until they make it a priority.

I know this is frustrating. We're looking into this issue and may have a fix in our next release. 

Thanks for your patience.