New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usage of 0 in Time Settings #1
Comments
Thank you, @moriel5 for this tricky bug. Importance: Will try to fix in next version. |
No problem, I'm glad to be of help. And I am certainly looking forward to testing the next version. |
Fixed in version 1.9 or later. Unit test added. Available in F-Droid, will be available in AppGallery soon. Thank you for participation. |
No problem, I'll test this now. Update: I can verify that 0 and decimals can no longer be entered on their own, even if I attempt to paste it from the clipboard. |
Oddly enough, since I wanted to try installing 1.8, breaking it, and then updating it, I found that the F-Droid 1.9 can not install on top of the F-Droid 1.8. Update: It is because the F-Droid 1.9 build was somehow compiled with Android 3.0 as the target (which explains the warning claiming it was built for older versions). I shall post this as a separate issue. |
Hello, I was curious, so I decided to test out the app, and since I usually try to test unreasonable values, I decided to try getting 0 to be accepted as a valid value (great job on preventing it outright, even if I type 2 digits and then remove the nonzero digit).
Putting in a value of .0 for Work Duration crashes the app, and prevents it from opening until the app's data is cleared.
Print in a value of .0 for anything else crashes the app, and makes the app's settings inaccessible until the app's data is cleared.
The text was updated successfully, but these errors were encountered: