[critical] continuous crashing of signal app in android 14
For last few days my signal application is crashing. I have tried to resolve the issue by deleting app data followed by erasing account and then reopening but this problem still persists. But in my another phone a signal on a different account is working smoothly. Please look into the issues
screenshot
screenrecord
https://github.com/user-attachments/assets/f089ca44-02f2-4198-aa55-28ee1613b818
device info:-
Model- Motorola edge 40 Android ver- 14 Signal ver- 7.14.2 Playstore version
7.15.4 updated reinstalled and deleted the account completely and reopened issue still exists. Don't know why it takes so much time to fix. As it os s major problem.critical in nature
Did you transfer Signal-account and data (chat history, etc.) from another device with Android 12 or 13?
Did you transfer Signal-account and data (chat history, etc.) from another device with Android 12 or 13?
No i did not.
Similar issue https://github.com/signalapp/Signal-Android/issues/13668 https://github.com/signalapp/Signal-Android/issues/13655 https://github.com/signalapp/Signal-Android/issues/13662 But i did not do any backup stuff.as i don't take backups. After this issue i have reinstalled signal and also reopened signal account after permanently deleting that. But issue still persists.
This is totally unusable can you loook into and provide a fix asap.
My SD card just died so I don't even have a current backup :/
I get this crash report:
android.database.sqlite.SQLiteDatabaseCorruptException: FullCode: 11 | ErrorCode: 11 | ExtendedErrorCode: 0 | Message: database disk image is malformed | ExtraMessage: null
at net.zetetic.database.sqlcipher.SQLiteConnection.nativeExecuteForCursorWindow(Native Method)
at net.zetetic.database.sqlcipher.SQLiteConnection.executeForCursorWindow(SQLiteConnection.java:881)
at net.zetetic.database.sqlcipher.SQLiteSession.executeForCursorWindow(SQLiteSession.java:871)
at net.zetetic.database.sqlcipher.SQLiteQuery.fillWindow(SQLiteQuery.java:68)
at net.zetetic.database.sqlcipher.SQLiteCursor.fillWindow(SQLiteCursor.java:196)
at net.zetetic.database.sqlcipher.SQLiteCursor.getCount(SQLiteCursor.java:135)
at org.thoughtcrime.securesms.database.SQLiteDatabase.traceSql(SQLiteDatabase.java:115)
at org.thoughtcrime.securesms.database.SQLiteDatabase.traceSql(SQLiteDatabase.java:95)
at org.thoughtcrime.securesms.database.SQLiteDatabase.rawQuery(SQLiteDatabase.java:353)
at org.thoughtcrime.securesms.database.ThreadTable.getUnarchivedConversationList(ThreadTable.kt:938)
at org.thoughtcrime.securesms.conversationlist.ConversationListDataSource$UnarchivedConversationListDataSource.getCursor(ConversationListDataSource.java:213)
at org.thoughtcrime.securesms.conversationlist.ConversationListDataSource.load(ConversationListDataSource.java:77)
at org.signal.paging.FixedSizePagingController.lambda$onDataNeededAroundIndex$1(FixedSizePagingController.java:111)
at org.signal.paging.FixedSizePagingController.$r8$lambda$W[...}4(FixedSizePagingController.java:0)
at org.signal.paging.FixedSizePagingController$$ExternalSyntheticLambda2.run(R8$$SyntheticClass:0)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)
at org.signal.core.util.concurrent.SignalExecutors$1.run(SignalExecutors.java:32)
at [[ ↑↑ Original Trace ↑↑ ]].(:0)
at [[ ↓↓ Exception Message ↓↓ ]].(:0)
at FullCode: 11 | ErrorCode: 11 | ExtendedErrorCode: 0 | Message: database disk image is malformed | ExtraMessage: null.(:0)
Signal v7.15.4 is now available on Google Play as well as our website. Please let us know if the crash is resolved.
This seems to be fixed i did not face this issue after the latest update still I won't close this i will keep testing for next 2days if everything works well i will close this thanks.
Signal v7.15.4 is now available on Google Play as well as our website. Please let us know if the crash is resolved.
No update available for me. Guess it would not be possible to update with an apk when it was installed via Play Store?
No update available for me. Guess it would not be possible to update with an apk when it was installed via Play Store?
You should be able to safely install the website APK over your Play Store installation, but out of an abundance of caution I would make sure to make a local backup and verify it. In addition, please play very close attention to your phone's prompts during the app upgrade, as it should warn you if you are at risk of data loss.
I can't create neither verify a new backup as it's not possible to open up the app. 😬
I am closing this issue as the issue has been fixed if any of you think problem persists let me know. I will reopen this.
Problem started again for my device so it is not fixed yet . Sometime it does not show any error message.But now It is impossible to open signal app.Even opening the account became impossible. I have tagged you for showing the videos of error @nicholas-signal Can you look into this. Many users are facing similar issues.
Video proof.
https://github.com/user-attachments/assets/654bd923-3553-4737-9aac-5e069005fbb8
Provide logs signal settings -> help -> debug logs Save and provide logs.
Dont you see the issue with your request yourself? 🤔😅 Just a have a look at your own video.
Cant understand can you elaborate what you want me to look for.
It's not possible to get any logs when Signal crashes instantly all the time.
Same here, on version 7.16.1.
It's very strange as it seems to work some times during the day, but when it starts crashing it keeps crashing no matter how many times I try it. Restarting the phone does not help. Once I received a notification about a new message and when I clicked the notification, it took me to that conversation without a crash. I also tried removing all data and starting fresh (without restore). I thought it solved it but today the same thing happens.
Edit: this workaround works for me, it opens Signal without crashing!
long press and select group message (a conversation)
If someone is still experiencing crashes on 7.15.4+, or had experienced crashes but they are now resolved, please upload a debug log (or ADB logs if the crashes are still happening).
If someone is still experiencing crashes on 7.15.4+, or had experienced crashes but they are now resolved, please upload a debug log (or ADB logs if the crashes are still happening).
I am facing this...
It's very strange as it seems to work some times during the day, but when it starts crashing it keeps crashing no matter how many times I try it. Restarting the phone does not help. Once I received a notification about a new message and when I clicked the notification, it took me to that conversation without a crash. I also tried removing all data and starting fresh (without restore). I thought it solved it but today the same thing happens.
The problem is this how i face it right now problem is not happening right now but i know it will start happening after sometimes later and this is impossible to get a log just look into the screen record I don't know how to do adb i am using fedora silverblue linux adb may not be supported in fedora. So I can't mainly I don't know about how to do adb.
@nicholas-signal https://debuglogs.org/android/7.16.1/31c753de63fa1ac0e19e408d828f265d63b3e5851995ef7676c14446a63b9a83
Edit: this workaround works for me, it opens Signal without crashing!
long press and select group message (a conversation)
Not possible for me, I'm not seeing a single chat until the crashes.
I would make sure to make a local backup and verify it.
Or is it possible to backup the app files manually?
I too am having this crashing issue. A week and half ago, on Monday August 26 (evening PST), Signal android phone app starting crashing. I believe that may have been Signal Version 7.14 Signal desktop app has been working perfectly fine this whole time. Signal Desktop is currently the only way I can use Signal. I live on Signal, I need the Android app working again on my phone.
When the problem first occurred, I was able to start the phone app, and even go into settings. But the app would crash as soon as I opened any chat. I was able to start a backup of chats, but the app would crash before completing the backup.
I signed up for the beta program to get quicker updates, hoping that would fix the problem. It hasn't. After updating to beta channel, now the android app crashes almost immediately. It keeps backing out. So if I'm quick, I can click my profile photo, click Account, and then click an option before the app quickly backs me back out repeatedly, until I reach the home screen. If I'm fast enough, I can struggle to move forward in settings while the app keeps backing me out, until it just crashes, and I get a message that "Signal keeps stopping". Clearly this is not usable.
Updating to the recent Version 7.15 or 7.16 has not fixed this issue.
Any help is very appreciated.
Should I create a new issue thread, or is it best to address this matter in this issue thread?
I love Signal, and I've been a huge advocate. I was turned onto Signal in 2016 by John McAfee in person, because he lived on Signal and didn't like to communicate elsewhere. I'm eager to get Signal working again on my phone.
Thank you so much for your help here.
@juddweiss Can you try opening the app in airplane mode?
I too am having this crashing issue. A week and half ago, on Monday August 26 (evening PST), Signal android phone app starting crashing. I believe that may have been Signal Version 7.14 Signal desktop app has been working perfectly fine this whole time. Signal Desktop is currently the only way I can use Signal. I live on Signal, I need the Android app working again on my phone.
When the problem first occurred, I was able to start the phone app, and even go into settings. But the app would crash as soon as I opened any chat. I was able to start a backup of chats, but the app would crash before completing the backup.
I signed up for the beta program to get quicker updates, hoping that would fix the problem. It hasn't. After updating to beta channel, now the android app crashes almost immediately. It keeps backing out. So if I'm quick, I can click my profile photo, click Account, and then click an option before the app quickly backs me back out repeatedly, until I reach the home screen. If I'm fast enough, I can struggle to move forward in settings while the app keeps backing me out, until it just crashes, and I get a message that "Signal keeps stopping". Clearly this is not usable.
Updating to the recent Version 7.15 or 7.16 has not fixed this issue.
Any help is very appreciated.
Should I create a new issue thread, or is it best to address this matter in this issue thread?
I love Signal, and I've been a huge advocate. I was turned onto Signal in 2016 by John McAfee in person, because he lived on Signal and didn't like to communicate elsewhere. I'm eager to get Signal working again on my phone.
Thank you so much for your help here.
I have recently installed https://github.com/mollyim/mollyim-android This is really good and find some advance feature also. Like use openstreet maps instead of gmaps.. Now i have suggested molly because this is a privacy enhanced fork of signal android. I know smae for me as i have uninstalled whataspp my lifeline was signal and as you can see from my video. Now i recommend you to like this main bug report to enhance and repeated bugreport does not help much but a comment does.
@juddweiss Can you try opening the app in airplane mode?
Doesn't work. Signal still crashes just the same in airplane mode.
Fyi, I'm using a Samsung Galaxy Z Fold 5
I have the same issue with the app and I am on 7.16.1 and it also happens with it in airplane mode, it behaves like this for the last two weeks, I am using it on a S22 with the latest security patch level.
Hi folks, 7.16.3 is out in beta now. If you're on the beta, please update and try again. Thanks for your patience with this!
Sadly Version 7.16.3 is still crashing. Is there anything I can do to more directly help the effort to solve this?
If anyone is able to capture the ADB output, can you see if it matches what we're seeing in #13673 ?
