Skip to content

Commit 71cd173

Browse files
authored
Make it more clear that the db corruption originates from an old AntennaPod version (#243)
1 parent 7d7dfec commit 71cd173

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

_i18n/en/documentation/bugs-first-aid/database-error.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
You might feel like screaming *Help! I lost my podcasts/episodes/settings/everything!*
22

3-
The problem is that the database with all information (episodes, listening states, etc) has some mistakes. AntennaPod cannot function with the broken database and had to start over with an empty one. While it's been happening less frequently in recent versions of AntennaPod, it still is occurring for some users. Our community of developers have not been able to pinpoint what exactly causes a database to break. The same issue occurs also in some other open source apps. But we realise it is very frustrating when this happens and are really sorry if you were affected too.
3+
The problem is that in a very old AntennaPod version, the database with all information (episodes, listening states, etc) had some problems. While the problems are long fixed, they might have left your database in a state that works but is slightly corrupted. With that corrupted database, the problem can manifest even in more recent versions if they happen to write to the corrupted parts (eg. during an update). If this happens, AntennaPod cannot function with the broken database and has to start over with an empty one. We realise it is very frustrating when this happens and are really sorry if you were affected.
44

55
There may be some things you can do to recover your data. We list them below, starting with the solution that gives the easiest & best results:
66

7-
1. Have you recently [exported a backup](/documentation/general/backup) from AntennaPod recently? Then restoring that is relatively easily: go to `Settings` » `Storage` » `Import/Export` » `Database import` and select the back-up.
8-
2. If you don't have a back-up, the next step is to attempt to recover the broken database ('repair corrupted sql database'). If AntennaPod detects a broken database, it writes it to a file CorruptedDatabaseBackup.db in the app storage directory. It is a challenge and it requires some skills or learning. You will have to use a terminal.
7+
1. Have you recently [exported a backup](/documentation/general/backup) from AntennaPod? Then restoring that is relatively easily: go to `Settings` » `Storage` » `Import/Export` » `Database import` and select the back-up. Note that the backup might contain the partial corruption, so it is still recommended to go through the second step to fix the problem once and for all.
8+
2. If AntennaPod detects a broken database, it writes it to a file named CorruptedDatabaseBackup.db in the app storage directory. You can attempt to repair this file (or repair an exported backup) using one of the steps below. This is a challenge and requires learning how to deal with a terminal.
99
* One community member [followed these steps](https://github.com/AntennaPod/AntennaPod/issues/2463#issuecomment-384088306) to repair the database and [indicated](https://github.com/AntennaPod/AntennaPod/issues/2463#issuecomment-404624614) that after this they could successfully import the repaired database.
1010
* Another community member [took a clean database and moved content from the corrupted one in it](https://github.com/AntennaPod/AntennaPod/issues/2463#issuecomment-385341068), and then performed [another correction](https://github.com/AntennaPod/AntennaPod/issues/2463#issuecomment-385354995). After both steps, they managed to successfully imported the new database in AntennaPod.
1111
3. While all the data *about* your subscriptions and episodes are gone, the media files will still be there.

0 commit comments

Comments
 (0)