-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
v7.17.1: Immediate Crash (invalid fts5 file format (found 0, expected 4 or 5) - run 'rebuild' | ExtraMessage: null) #13693
Comments
Having exactly the same issue with 7.17.1. Same as 7.16.4, just crashes faster. Completely unusable. Samsung S21 |
Same issue on 7.16.4, Samsung S23. Unusable. |
Thanks folks, looks like the hopeful fix for the fts file format crash didn't quite catch everything. We'll get another attempt out in 7.17.2 soon. |
|
Submitting a 7.17.2 to the play store today, will likely crash once again after updating, but that should trigger the repair and the second start should work. |
Since it seems to take quite a while for Google Play Store to roll out updates (7.17.1 still has not arrived on my device, and it's already 3 days old), will 7.17.2 also be available from https://signal.org/android/apk/ (in addition to submitting it to the Play Store) for immediate (manual) update? |
v7.17.2 fixed the issue. Thanks a lot! |
Figured it out: 7.17.1 and 7.17.2 are beta versions. I had to join the beta programme via Google Play, wait several hours until it offered the update to me, update, then leave the beta programme again. |
Duplicate of #13675 |
To my non-signal-dev eyes, those issues are not duplicates:
|
Is there any expectation when the update will be available at https://signal.org/android/apk/? Further: since Signal keeps crashing directly, will the app be able to update automatically on its own? Or will I need to reinstall the app? At the moment I am still hoping to preserve contacts and messages that are only saved within my signal app and not backed up but since I rely heavily on using the app and it has not worked for my anymore since Sunday, I would appreciate an indication if it's worth waiting or if that data will be lost anyways. |
@pneutig Traditionally we update the website once the play store is rolled out to 100% (we rely on the play store rollout to catch bugs, since our website build has no rollout mechanism). However, given the circumstances, I've just kicked off a build now, so it should be available in 15min or so. If you have the same issue as everyone else in this thread, you will not lose any data. You will likely need to install the build from the website manually, as the auto-update mechanism won't work. Hope that helps! |
@greyson-signal Thank you very much! I can indeed confirm that the update helped and my Signal app is working again. Unfortunately, messages which could not be delivered between the beginning of the problem and the update have so far not caught up (roughly 18h after update) but at least the app itself is working again. |
Bug description
Launching 7.17.1 results in a crash after showing the signal logo. Unlike #13685, the app crashes before showing the home screen.
Steps to reproduce
Unclear
What I know:
Screenshots
Device info
Device: Fairphone 3
Android version: 13 (/e/OS 2.3-t-20240816426372-stable-FP3)
Signal version: 7.17.1
Link to debug log
Because Signal crashes immediately, captured via
adb logcat
:The text was updated successfully, but these errors were encountered: