-
Notifications
You must be signed in to change notification settings - Fork 608
[Firestore] SQLite error: duplicate column name: target_count #134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you confirm that other devices have not had an issue? Is it just these 3? We have not been able to reproduce the issue, so I would like to figure out if it is something specific to a couple of devices or if it is a more general bug. |
Yes, currently I have seen only these 3 devices producing this crash. |
Hmm, that does unfortunately sound device-specific. I will continue to investigate. In the meantime, if anyone else has seen anything like this, please chime in, I'd love to get more details on exactly what scenario triggers this exception. |
@saurabhdtu i am investigating one possible, non-device-specific cause. Is there any chance that you at some point shipped a version of your application that downgraded the Firebase SDK version? For example, if you shipped your app with Firebase It looks like that is one way that schema migrations could end up running more than once. |
I'm having the same issue today on two different phones, both were working fine yesterday. The issue happens on both an Essential Phone I have and a Galaxy S9. Tried downgrading to 17.1.2 and 17.1.0, same thing, so it seems unrelated to the version of the sdk. I'm not sure what triggered the issue this morning, but I'm unable to run my Firestore app successfully at all this morning due to this issue. Enabling offline persistance gives me: #115 Signing out the currentUser in FirebaseAuth on app launch and the signing in does nothing, same issue, same thing with clearing appdata/cache, same problem. So I can't seem to get it working at all today. Firestore offline persistance: false Firebase gradle dependencies: Stacktrace:
|
The error you've posted above is unrelated to this issue. This issue is about the client apparently re-running schema migrations on startup (i.e. this exception):
The stack trace you've posted above indicates multiple processes are trying to access the same database at the same time.
Disabling offline persistence should not access SQLite at all. Could you post the code you're using to disable persistence in a new issue? Also, the stack trace shows proguarded symbols, which indicates you're not on the latest release (we disabled it in our builds in 17.1.2). Could you re-try with the latest version (17.1.3)? |
Ok, I can confirm I've been able to reproduce this by using the following sequence of SDK versions: |
A fix was released with Firestore 17.1.5. Firestore will now properly record that it's downgrading. Unfortunately, all previous releases don't do this so downgrades across schema versions aren't safe and can result in similar errors. |
Getting the crash with SQLite operations
I have seen it occurring on fabric for specific devices:
Oppo CPH1823-(8.1.0)
Karbonn K9Smart1GB -(5.1)
Micromax Q394 -(5.0.2)
Stacktrace:
Issue #: 4816
Issue ID: 5b13ee2d6007d59fcdc643ee
Session ID: 5BF1ADC9017D000173511635EF2E7A9B_DNE_0_v2
Date: 2018-11-18T18:22:00Z
OS Version: 5.0.2
Device: Canvas Juice 3+
RAM Free: 34%
Disk Free: 26.6%
The text was updated successfully, but these errors were encountered: