InvalidKeyException: Error executing SQL: file is not a database
Categories
(Fenix :: Logins, defect, P5)
Tracking
(Not tracked)
People
(Reporter: svillar, Unassigned)
Details
(Keywords: crash)
Crash Data
Steps to reproduce:
This comes from https://github.com/mozilla-mobile/android-components/issues/6681
We upgraded Wolvic to v75 as we were told that no more crashes were reported after that version. The truth is that from our early testing this is still an issue in v75.
Steps:
- Setup FirefoxAccounts synchronization in Wolvic. Let it sync pass,history...
- Update Wolvic to a newer version
- Launch updated Wolvic
Actual results:
App crashes with the trace described in github
Expected results:
No crash :)
Reporter | ||
Comment 1•2 years ago
|
||
:jonalmeida it looks like the bug is still there in v75 at least.
Comment 2•2 years ago
•
|
||
As mentioned in the initial issue, there are 2 possible reasons for this:
- The encryption key for the database was lost, missing or corrupt.
- The sql database on disk is corrupt.
[edit - fix formatting]
- isn't possible in newer versions of Fenix as we no longer use sqlcipher and instead use plain old sqlite. I can't recall what version this changed in.
- We still don't handle corrupt sqlite databases - if they happen the exact message is now likely to be different, but we do still see these errors for all our databases.
Comment 3•2 years ago
|
||
The severity field is not set for this bug.
:cpeterson, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 4•2 years ago
|
||
There haven't been any crash reports since Fenix 91.
Reporter | ||
Comment 5•2 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #4)
There haven't been any crash reports since Fenix 91.
Which AC version was it shipped with? We're able to reproduce it easily with v75
Updated•2 years ago
|
Comment 6•2 years ago
|
||
Closing as WFM because there have been no crash reports since Fenix 89.
Description
•