![]() and-bible |
||
---|---|---|
.. | ||
README.md | ||
and-bible-3.0.286-#261.apk | ||
and-bible-build-309-#375.apk | ||
and-bible-build-327-#480.apk | ||
and-bible-build-369-#697.apk | ||
and-bible-build-377-#703.apk | ||
class_files.json | ||
crash_stack_#261.txt | ||
crash_stack_#375.txt | ||
crash_stack_#480.txt | ||
crash_stack_#697.txt | ||
crash_stack_#703.txt | ||
script-#261.py | ||
script-#375.py | ||
script-#480.py | ||
script-#697.py | ||
script-#703.py | ||
video-#261.mp4 | ||
video-#375.mp4 | ||
video-#480.mp4 | ||
video-#697.mp4 | ||
video-#703.mp4 |
README.md
Note: Install node.js from http://nodejs.org/ for building the app.
For Issue #697 (this is a severe regression bug)
The key step to repro this bug:
-
open a bible book and scroll up to the first chapter
-
long click on the text at the very beginning
-
click the pen icon on the menu bar to create a note with content (e.g., "hello"), and save the note
-
reopen the note via the pen icon in the verse (the note is empty, this is already a sign error, the first error stack trace appears)
-
input new content (e.g., "world"), and save (press back key to save), the current page shows "An error has occurred. Report a bug" (the second stack trace appears).
-
go to the main menu and click the note option, the app crashes (the third AndroidRuntime stack trace appears).
For Issue #261:
The user has to download a bible first and then download a book before he can go to view the book.
For Issue #480:
The basic functionality of creating and modifying labels is correct. The crash can be triggered only when the first label was created and deleted it. After the crash happens, the basic functionality cannot be used anymore (i.e., modifying labels will just crash). In addition, We find the crash can be reproduced when renaming the empty labels (do not need to do the remaining steps in the bug report).