HabitKit Will Not Open, Or Shows An Error
By Sebastian Röhl, creator of HabitKit
6 min read Published Updated Instructions for HabitKit 1.19.0
Do not uninstall HabitKit while trying to recover your data. Uninstalling removes the local database and on-device backups; only the daily iCloud backup (iPhone) or Google Drive backup (Android), if it is on, survives.
If you see Your data couldn't be opened, unlock the phone, check that storage is available, and tap Try again. The file is still on the device. If retrying fails, read the recovery choices below before restoring a snapshot; a restore can exclude more recent entries.
On this page
The Recovery Screen
The full text reads: HabitKit couldn't open its database. Your habits are still stored on this device, but the app can't read them right now. When HabitKit knows why, a line underneath says so, such as "Your device is almost full. Free up some space, then try again." or "This data was saved by a newer version of HabitKit. Update the app, then try again."
Try again is the first button, and it is worth more than one attempt, because the usual causes pass. A device with no free storage cannot open a database for writing. Neither can an iPhone or iPad that has not been unlocked since it last restarted, because iOS protects app files while the device is locked. Free up some space, unlock the phone properly, then try again.
Below it, HabitKit looks through the automatic backups on the device ("Checking for a usable backup…") and offers the newest one it can actually read. It shows what that backup holds, such as "5 habits and 1,204 check-ins from yesterday at 09:14 will be restored.", with a Restore this backup button. Restoring keeps your original database on the device and brings your habits back from that backup, so later changes are not included. Backups are created when you use the app; the newest usable one may be older than yesterday. If none can be used, the screen says "No usable backup was found on this device. Your stored data has been kept." Nothing is moved or replaced then, and Try again stays available. Contact support rather than uninstalling. Automatic backups, and how to restore one explains what the snapshots contain and how far back they go.

Illustrated recovery choices. Try again comes first; Restore this backup appears only once a usable backup has been found.
Other Error Screens
Not every error is that one, and most of them are milder.
Something went wrong, followed by "Your habits couldn't be loaded." and a Try again button, means the habit list failed to load. That message alone does not tell you whether data is missing. Tap Try again, and if that does not clear it, close the app fully and reopen it.
A Pro screen that will not close is usually a slow connection rather than a stuck screen. Its initial purchase-status check has a 25-second timeout, but a restore or purchase may take longer. Give the store time to respond. If the screen remains unresponsive, reopen the app on a working connection. If the problem is that you already paid and the app disagrees, restore a Pro purchase is the article you want.
A launch screen that never ends. The 1.19.0 instructions here describe the recovery screen. If you are on an earlier version and remain on the splash screen, update to the current version. If the issue continues, contact support without uninstalling.
If it is one day that looks wrong rather than the whole app, see a day you completed looks empty or missing instead.
Before You Write In
In roughly this order, and in this order for a reason:
- Update to the latest version. A good share of what people report has already been fixed.
- Force quit HabitKit and reopen it.
- Restart the phone.
- Check you have free storage. A full device causes problems that look nothing like a full device.
- If you can still open the app, export your data and put the file somewhere safe before you change anything else. Export is free.
Sending A Useful Bug Report
Use Settings › Send feedback, in the Help section, rather than writing to us from scratch. It opens an email draft that already contains your operating system and its version, your device model, the app version, and the identifier we use to look up a purchase. Type your message above that block and leave the block alone.
Then add, in your own words:
- what you tapped
- what you expected
- what happened instead
- whether it happens every time or once
- a screenshot, or a short screen recording if it is a timing problem
For a widget problem, say which widget you are using and, on Android, whether Legacy (Performance) Mode is switched on at Settings › General, in the Home Screen Widgets section. Widget not updating is worth reading first.
One thing worth knowing about what we already have: crash reports are on by default, and you can turn them off at Settings › General, in the Debug section at the bottom, with the switch labelled "Allow Crashlytics". A crash usually reaches us on its own. A screen that looks wrong without crashing does not, which is why the description above matters more than you would think.
If you would rather not use email, the support page has the other ways to reach us.
Related Questions
Will "Restore This Backup" Lose Data?
A successful restore returns to the saved backup and excludes later changes. The original database is kept on the device either way. If no usable backup is found, nothing is restored and your stored data stays where it is; do not uninstall, and contact support.
Should I Reinstall HabitKit To Fix It?
Not before exporting. Uninstalling removes HabitKit's data from the device, including the daily backups on it. A recent iCloud backup (iPhone) or Google Drive backup (Android) can be restored after reinstalling, if it is on. Export first, then reinstall, then import.
What Should I Include In A Bug Report?
Send it from Settings › Send feedback, in the Help section, so the device and app details come along automatically. Add what you tapped, what you expected, what happened, whether it repeats, and a screenshot if you have one.