Entering habit via notification when clock is set to epoch 0 crashes the app irremediably

[7heo]

Pre-submission checklist

• I am submitting a bug report, not a feature request.
• I have searched for similar issues, but did not find any matches.

Description

My phone started, the clock was set to epoch 0, and uhabits generated notifications (I have no habits data entered for Jan the 1st, 1970). I didn't pay attention to the "53y" due date in the notification and entered my habit.

Now the app won't open. It straight crashes when opening. No display, no nothing. Absolutely unusable. It's a shame, this app is otherwise one of the best ones I ever used. I hope this can be fixed soon, because I don't think I can use the app until it is 😢

I suspect it is possible to totally reset the user data and get the app to work again, but I do not want to lose all my progress. I have been using this app for years.

Steps to reproduce

1. Set the clock to epoch 0
2. Wait for habits notifications to appear
3. Use a notification to enter the habit
4. Try and open the app
5. App doesn't open again.

System information

• Phone Operating System: Android 8.1.0 / LineageOS 15
• App version: 2.1.1

[7heo]

So just to be thorough, I was able to locally "solve" this issue by opening the sqlite database of the app, and deleting the relevant entries:

phone:/data/data/org.isoron.uhabits $ sqlite3 databases/uhabits.db
SQLite version 3.19.4 2018-12-19 17:05:48
Enter ".help" for usage hints.
sqlite> SELECT * FROM Repetitions WHERE timestamp = 0;
4460|16|0|0|
sqlite> DELETE FROM Repetitions WHERE id = 4460;
sqlite>
phone:/data/data/org.isoron.uhabits $

After this, the problem was solved. I could use the app again, normally.

[hiqua]

For completeness, how did you end up with epoch 0 on your phone?

It's definitely a bug, but hopefully it should be rare enough to be lower priority.

[7heo]

It happened right after boot. I have a very old phone that has a battery that dies pretty hard sometimes, there is no SIM in the phone, and it can take a while to connect to the WiFi.

So I suppose it was after a cold reboot, with zero battery charge left to maintain the RTC state. and the OS just went with "epoch zero" as it had no way to determine it any better. The OS booted, I got a bunch of notifications, unfortunately validated one, and created a DB entry with epoch zero. I couldn't delete it anymore since the app crashed, and also since the phone then got up to date (pun intended) time.