Problems with Bible App 5.5.5 on Android 6 Tablet
PROBLEM 1: Cannot add text in a note
Reproduction Steps
1. Add or Edit a note
2. Type anything in the main body of a note
Result:
The letters appear as you type (as usual), but when space is pressed to type the next word, the word you just typed is erased and replaced with a space.
Expected Result:
The words you type would not be erased.
Other Info:
Typing works correctly in the title of the note.
If the predicted word (above the keyboard) is pressed, then the word is entered as expected.
If I turn off predictive text in my keyboard settings, then words are entered correctly and not erased.
This is not a problem I have in any of my other apps.
Also, Bible Notes work fine on my Android 5 Phone using version 5.4.6 (Build 504060160).
PROBLEM 2: Reading Plans do not show dates - only 'week 0', 'week 1', etc.
Reproduction Steps
1. Create a new Reading Plan
2. Join Plan on Tablet (if created elsewhere)
3. Go to Menu > Documents > Click Plan
Result:
Both the Overview and List Views show the dates as "Week 0", Week 1", etc. as opposed to showing the actual date for each.
Expected Result:
The Reading plan should show the actual date for each passage.
Other Info:
The Desktop version, iPhone version, and version 5.4.6 on my Android 5 Phone all correctly show the actual dates on the same reading plan (it is a shared plan thru a faithlife group).
I also created a new reading plan on this Tablet, to read by myself, using the NIV84 Bible (above plan used NASB95) and got the same results:
Same Plan on my Android 5 Phone (Bible Version 5.4.6):
...............................................
Detailed Device Information
- Asus P00A P00A_2 - ZenPad Z380M-A2-GR
Detailed Android version
- Android 6.0
Faithlife App name and version
- Bible 5.5.5 (Build 505051310)
The Resource you are using (if applicable)
- Any Bible (tested with NASB95 & NIV84)
Bill,
Thanks for reports. The second issue appears to be a regression so I've reopened that case. Regarding the first issue, have you tried a different keyboard (like the Google keyboard)? We've occasionally seen keyboard related issues when a vendor specific keyboard is being used.
In the future please try to create a new thread for each bug report. From https://community.logos.com/forums/t/118701.aspx : "One bug, one thread (this makes it easier to link your thread to our bug tracking system)."
Thanks for your prompt reply Kevin,
Looking forward to having the reading plan dates put back, in the mean time I'll make sure I don't let my phone update the Bible app.
I installed the Google Keyboard and it does work, no problems! I still hope you all will be able to fix the problem with the Asus Keyboard though so I can go back to using it.
Also, next time I'll post separate issues in separate threads, sorry about that.
Still a problem with newest version 5.6.2
Any progress on either of these issues?
Note editing is now worse, no matter what I do your app erases the words I type, even with predictive word off. Just reiterating... no other apps have any problems typing words with the Zen keyboard. This is an issue with your app not my keyboard.
The lack of a date in reading plan does appear to be an android 6 issue, as I updated my android 5 phone to Bible 5.6.2 and it does not exhibit this behavior.
A case already exists, and the current workaround is to use the Google keyboard. We don't give ETA's or progress reports on which bugs we're working on.
As mentioned above, a case already exists for this one. When it's fixed it will be mentioned in the release notes.
Ok, glad a case has been opened on this - you didn't mention this before. Look forward to this being fixed someday.
I thought it would be helpful to confirm that this is a problem specific to android 6. But if not, ok.
Just wanted to post something to let you know dates in reading plans are still showing weeks instead of the actual date (in android 6). This was reported back in September - 4 MONTHS AGO!
It is the kind of issue thatnever should have made it through beta and yet it's still not fixed after 4 months.
Is anyone actually going to do anything to address this???