Reported by a user via e-mail....

The application crashed...

All the 'good' filters had this in INFOVALUE:

{
"FILTER": "View All Transactions"

}

There was one 'bad' filter with only a number in INFOVALUE, deleting this row fixed the crash it.

7

User said

"I checked my old v1.4 DB and it had the same value, number 7.

This is just a guess on my part, "7" is supposed to reference a filter preset?
However filter preset 7 says it's empty, at least in the app. (Don't know where to look for numbered filter presets in the DB, I can check if it's really empty if you point me in the right place.)

Another guess: v1.4 was fine with referencing an empty filter preset, but v1.7 crashes.

Maybe you could add to the DB downgrade script to clear filter numbers which reference empty filters?
Or check filters on startup, and revert them to default if the referenced filter number preset doesn't exist."