2.1.2 (Build 57): "Navigation failed" trying to go to "Today's Reading" in any lectionary
1. Open any lectionary. The one I use most often is Book of Common Prayer (1979) Daily Office Lectionary, but this problem occurs in other lectionaries as well (e.g., Catholic Lectionary).
2. Navigate to the Title page
3. Tap "Today's Reading"
Result: I get a "Navigation failed" error.
Note that in Logos 4 Windows, when you open a lectionary, it goes automatically to today's reading. I would expect the Android app to work that way too. But barring that, at least fix this navigation problem so I can get to Today's Reading from the Title page. (I can navigate there laboriously through the TOC, but to do that I need to know what "Proper" we are in this week, which I don't know normally off the top of my head.)
Comments
-
Hi Rosie,
I covered this issue in the iOS thread - it's already written up. Thanks!
0 -
Hi Rosie,
I covered this issue in the iOS thread - it's already written up. Thanks!
I figured it was a separate issue, because this is Android and I thought they were on separate code bases. And besides, the result in this case is "Navigation failed" where as on the iOS app it goes back to the beginning of the resource.
0 -
Hi Rosie,
I covered this issue in the iOS thread - it's already written up. Thanks!
I figured it was a separate issue, because this is Android and I thought they were on separate code bases. And besides, the result in this case is "Navigation failed" where as on the iOS app it goes back to the beginning of the resource.
Yes - iOS and Android are separate code bases but this issue is common to both platforms. The navigation fails on both, it's just that iOS doesn't specifically tell you like Android does. Hopefully we can get this fixed sooner rather than later since there are quite a few resources it affects.
0 -
Hi Rosie,
I covered this issue in the iOS thread - it's already written up. Thanks!
I figured it was a separate issue, because this is Android and I thought they were on separate code bases. And besides, the result in this case is "Navigation failed" where as on the iOS app it goes back to the beginning of the resource.
Yes - iOS and Android are separate code bases but this issue is common to both platforms. The navigation fails on both, it's just that iOS doesn't specifically tell you like Android does. Hopefully we can get this fixed sooner rather than later since there are quite a few resources it affects.
Well if there are two different teams working on the two different code bases, the problem will need to be fixed twice, even if the fix is the same in both places, so that's why I felt it was important to get it on the bug list for both apps. If the iOS team fixes the bug and the Android team doesn't, I would feel I had failed in bringing it to their attention. But since you assure me both teams know about this problem and are planning to fix it (hopefully sooner rather than later) I think I can rest easy now.
0
