Daily Reading Glitch
daily reading is available on the home screen and opens the passage, but the blue bars showing the start and finish aren’t visible. I uninstalled the beta and installed, but now the daily reading (read wave in a year) constantly opens le Hal and doesn’t show the blue bars.
Comments
-
Quick update...the beta before this current version (8.6.0.0047) worked as expected. With this new update (on both iPad and iPhone), the daily reading markers in my preferred Bible (ESV) are not visible. I have to navigate to the “Readings” tool to check off the reading.
0 -
Kennett and I have seen something similar - see https://community.logos.com/forums/t/184785.aspx for another discussion of it.
And there, Todd said they will work on getting it fixed.
I think from your description that you are seeing the same problem we are experiencing.
0 -
Yes. Thank you!
By the way... the .49 update solved it for me!
0 -
By the way... the .49 update solved it for me!
Me too[:)]
0 -
While the “banner” for the daily reading seems to be fixed in .49, I am now getting notifications from Logos to not “forget my daily reading.”
However, I have already completed my daily reading. In fact, when I open the app, the banner shows it is completed. And what I open the daily reading document it shows it is complete.
0 -
Quick update...I am now on build .54, and I have not seen this symptom repeat.
0 -
Posted that too quickly...
This morning, I received notification in Notification Center that my daily reading was not complete:
Here is verification my reading plan is already complete:
I am using .54 build...
0 -
Jeff, sorry, but that local notification just fires off every day at the time you set. There isn't currently any logic that removes a pending notification if you have read ahead.
0 -
Todd,
Thanks so much for the reply. That makes sense...though I never saw this notification until I have been using the beta. Could be that the install defaulted to certain notifications that I had turned off with the production build...or something else on my end that started these notifications.
Thanks again.
0
