About 30min ago I got Signal update 7.32.1 via the updater in the direct download APK. Now the app closes itself within a second or two every time I open it. No other changes and it worked just fine beforehand. I rebooted the phone without change. Am I the only one?
Signal crashing after update
Albatross
Maybe you give the newest version 7.32.2 a try?
On my Pixel 7 Pro I had no issues (GOS release 2025012700 or older) with Signal v7.32.1 or older.
Same with the newest Signal version.
I am using Obtainium to get the original version directly from Signal's repo at GitHub:
https://github.com/signalapp/Signal-Android/releases
Eagle_Owl I downloaded Signal as an .apk directly from the "danger zone" on their page and of course it has an in-app update function. Since years. https://signal.org/android/apk/
@Albatross I have version 7.32.1, too, and have or had no crashes on my Pixel 6 with the newest GrapheneOS version.
malatoi
Hello malatoi,
I have just compared the fingerprints of the APK version from Signal's website (‘danger zone’) with the version I have installed from Signal's repository (GitHub) and they are identical.
So we are obviously using the same version of the Signal app, but I don't see a menu for an update function in the app and this app has never updated itself or pointed out a new version for me to then manually trigger the update.
Very strange...
Eagle_Owl I have just compared the fingerprints of the APK version from Signal's website (‘danger zone’) with the version I have installed from Signal's repository (GitHub) and they are identical.
So we are obviously using the same version of the Signal app [.…]
If fingerprints of the files were compared (with shasum etc.), then the files are likely the same, though comparing the files directly (with, e.g., cmp) would be simpler.
If the fingerprints of the signing keys were compared, that means the files were signed by the same key, not that they are identical in behavior, or not even that they are the same app.
de0u
Thank you, that's right!
I have compared not the fingerprints of the files.
Then maybe the APK from Signal's “danger zone” has an in-app update function and is not identical with their version on GitHub…
BTW: their version in GitHub has a higher version number (v7.32.2 instead of 7.32.1 in danger zone)
fid02 I submitted a report to Signal, here's the log, seems like the db got messed up somehow with a non-unique entry. Not sure how that would be possible.
`type: crash
osVersion: google/raven/raven:15/AP4A.250105.002/2025012700:user/release-keys
package: org.thoughtcrime.securesms:150800, targetSdk 34
process: org.thoughtcrime.securesms
processUptime: 2468 + 306 ms
installer: org.thoughtcrime.securesms
org.thoughtcrime.securesms.migrations.MigrationJob$FailedMigrationError: android.database.sqlite.SQLiteConstraintException: FullCode: 2067 | ErrorCode: 19 | ExtendedErrorCode: 8 | Message: UNIQUE constraint failed: message.date_sent, message.from_recipient_id, message.thread_id | ExtraMessage: null
at org.thoughtcrime.securesms.migrations.MigrationJob.run(MigrationJob.java:46)
at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:88)
at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:51)
at [[ ↑↑ Original Trace ↑↑ ]].(:0)
at [[ ↓↓ Exception Message ↓↓ ]].(:0)
at android.database.sqlite.SQLiteConstraintException: FullCode: 2067 | ErrorCode: 19 | ExtendedErrorCode: 8 | Message: UNIQUE constraint failed: message.date_sent, message.from_recipient_id, message.thread_id | ExtraMessage: null.(:0)
Caused by: android.database.sqlite.SQLiteConstraintException: FullCode: 2067 | ErrorCode: 19 | ExtendedErrorCode: 8 | Message: UNIQUE constraint failed: message.date_sent, message.from_recipient_id, message.thread_id | ExtraMessage: null
at net.zetetic.database.sqlcipher.SQLiteConnection.nativeExecuteForChangedRowCount(Native Method)
at net.zetetic.database.sqlcipher.SQLiteConnection.executeForChangedRowCount(SQLiteConnection.java:818)
at net.zetetic.database.sqlcipher.SQLiteSession.executeForChangedRowCount(SQLiteSession.java:758)
at net.zetetic.database.sqlcipher.SQLiteStatement.executeUpdateDelete(SQLiteStatement.java:90)
at net.zetetic.database.sqlcipher.SQLiteDatabase.updateWithOnConflict(SQLiteDatabase.java:1871)
at org.thoughtcrime.securesms.database.SQLiteDatabase.lambda$updateWithOnConflict$16(SQLiteDatabase.java:404)
at org.thoughtcrime.securesms.database.SQLiteDatabase.$r8$lambda$qx1dYAO84QSSLaHe5_pqljq0bWk(SQLiteDatabase.java:0)
at org.thoughtcrime.securesms.database.SQLiteDatabase$$ExternalSyntheticLambda13.run(R8$$SyntheticClass:0)
at org.thoughtcrime.securesms.database.SQLiteDatabase.traceSql(SQLiteDatabase.java:113)
at org.thoughtcrime.securesms.database.SQLiteDatabase.updateWithOnConflict(SQLiteDatabase.java:404)
at org.thoughtcrime.securesms.database.SQLiteDatabase.update(SQLiteDatabase.java:261)
at org.signal.core.util.UpdateBuilderPart3.run(SQLiteDatabaseExtensions.kt:443)
at org.signal.core.util.UpdateBuilderPart3.run$default(SQLiteDatabaseExtensions.kt:441)
at org.thoughtcrime.securesms.database.MessageTable.remapRecipient(MessageTable.kt:4823)
at org.thoughtcrime.securesms.database.RecipientTable.merge(RecipientTable.kt:4019)
at org.thoughtcrime.securesms.database.RecipientTable.merge$default(RecipientTable.kt:4001)
at org.thoughtcrime.securesms.database.RecipientTable.mergeForMigration(RecipientTable.kt:3994)
at org.thoughtcrime.securesms.migrations.DuplicateE164MigrationJob.performMigration(DuplicateE164MigrationJob.kt:106)
at org.thoughtcrime.securesms.migrations.MigrationJob.run(MigrationJob.java:42)
at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:88)
at org.thoughtcrime.securesms.jobmanager.JobRunner.run(JobRunner.java:51)`
- Edited
I am seeing an open issue from about 1yr ago here:
https://github.com/signalapp/Signal-Android/issues/13421
I do not have the same situation, though, re: new contact. And ironically, I can receive but not send messages when I get Signal to stay open, whereas in the report the user can send but not receive.