Safer Database Updates in v1.3.20

Every time we add a new feature to Kepthouse — vehicles, properties, pets, EPC data, MOT history — the database that holds your data needs to be updated to support it. These updates are called migrations, and until now they happened silently in the background. If something went wrong, the app crashed. No warning, no explanation, no way to recover.

We have seen a small number of crashes in production caused by exactly this. A migration fails partway through, the app closes unexpectedly, and the user has no idea what happened or what to do. That is not good enough.

Starting with v1.3.20, database updates are handled completely differently.

What changed

You see what is happening

When an update is needed, Kepthouse now shows a dedicated screen before anything else loads. It tells you what is happening and lets you decide when to proceed.

The migration screen explains what is happening and waits for your input

Your data is backed up first

Before any changes are made, Kepthouse creates a local copy of your database. This is a temporary safety copy — it does not use your Google Drive backup slots. If the update fails for any reason, your data is restored from this copy automatically. You never lose anything.

Progress is visible

While the update runs, you see a spinner and a status message. No more wondering if the app has frozen.

Real-time status while the update runs

Failures are handled, not hidden

If an update does fail, you see a clear error screen instead of a crash. Your data has already been restored from the backup. The screen shows what went wrong and includes a one-tap button to email our support team with full diagnostic details attached — your app version, device model, Android version, the exact error message, and which database versions were involved.

Clear error details with one-tap email to support

Background tasks wait their turn

Kepthouse runs several background tasks — reminders, automatic backups, vehicle and property data refresh, geocoding. Previously, these could start before the database update finished, potentially hitting the database while it was mid-migration.

Now, every background task checks a safety gate before accessing any data. If the gate is closed (because a migration is in progress or has not run yet), the task pauses and retries later. No data access happens until the update is complete. No missed reminders either — they run as soon as the gate opens.

What does this mean for you?

If you are one of the users who experienced a crash after updating Kepthouse, we are sorry. That should never have happened silently. From v1.3.20 onwards:

• You will always know when a data update is happening
• Your data is backed up before any changes
• If something fails, your data is restored and you can reach us directly
• Background tasks cannot interfere with the update
• No more unexplained crashes

We take your data seriously. Every item, warranty, contact, and photo you have added to Kepthouse matters. This update is about making sure it stays safe, even when things go wrong behind the scenes.

Also in v1.3.20

• More backup versions — Premium users can now keep up to 30 backup versions on Google Drive (up from 10). The default stays at 10, adjustable in Settings.
• Scrollable backup list — the restore picker now scrolls so you can reach older backups.

Get the update

Kepthouse v1.3.20 is available now on Google Play. If you have not tried Kepthouse yet, it is free to download with 15 items included.

Get Kepthouse on Google Play →