Database corrupted

LBLB

WorkingHours constantly crashes when database get's corrupted due to whatever reason. Reinstalling and importing the database does not work. In my case error message is: item with key 0 already exists. Manually editing the database to check for possible errors or rescue data is not possible.

WorkingHours version: 2.7.2
OS + version: Android 11

timo

This is likely because a bug in an old version of WorkingHours that has been fixed in the meantime. I can fix the database for you - just write me a mail please, thanks 🙂

LBLB WorkingHours constantly crashes when database get's corrupted due to whatever reason

Can you please specify "constantly" in more detail?
When it crashes, how do you get access to the database then?
When you are using a "non-crashing" database, how long does it take until it crashes again?
As I've said, there shouldn't be any bug in the latest version causing the problem

LBLB

Currently, I am not even able to start a fresh install. Starting screen shows up for a second and closes again. No chance to open the app. Just before I wrote the issue I was able to open the app and try to restore the database.
Steps I took:

Got periodically messages of WorkingHours crashing.
Uninstalled the app
Reinstalled the app
Opened it - all data was gone
Tried to restore - described problem but able to open the app
Without having had success to restore one day later app again crashes
No success with reinstalling to open the app again - cleaning data doesn't help either

timo

If the app crashes after a fresh install this is an indication that there is some Windows problem. I don't see any crashes (that I could fix) in my crash reporting tool and haven't heard from other users having problems launching the app recently.
I personally would recommend doing a clean Windows install.

As I said, I can fix the import problem ("item with key 0 already exists"), but please write me a mail for this.

LBLB

As you can see in my initial post, it's not a Windows problem.

Added the stack trace. Seems like it's connected to the key error.

Don't want to send my personal data that got corrupted due to an app error. As it first appeared the last few days, I doubt a direct relation with an earlier version (Last update 09.09.21). Also the relevant database was created in the end of August so this error from my perspective could at most be caused by the Android version before this one. But again it must be mentioned that the error first occurred at the end of October so this issue should definitely be investigated in detail as a direct relationship is at least questionable.

timo

Sorry for getting confused with Android & Windows. Perhaps the app is crashing after reinstalling because Google automatically restores the app data.
I don't quite understand what you expect me to do in this situation.
I don't think there's a bug in the app causing corrupted databases. At least I would not know how to reproduce it. And as long as I can't reproduce it, I can't fix anything.

LBLB

From my perspective a corrupted database shouldn't lead to a complete crash of the app. At least ignoring the database in order to allow restoring Backups should be the minimum expectation. In addition, even ignoring only the possibly corrupted entries and reporting this behaviour could be a feasible measure. Best case would be a individual decision on how to handle (and maybe repair) corrupted entries.