Signal crashed on opening a thread

Pixel4XL_John

After having used Signal on Graphene OS for years, today I can't open thread.

So Signal starts and I see the list of person I chat with, but when I open a thread a short moment I see the contents of the thread and then it quits.

See the error message below.
Anyone any suggestions?

Pixel 4XL,
Version: TP1A.221005.002.B2.2024080800

I tried to install an older version, but then I get the message that I can't downgrade.

type: crash
osVersion: google/coral/coral:13/TP1A.221005.002.B2/2024080800:user/release-keys
package: org.thoughtcrime.securesms:145600
process: org.thoughtcrime.securesms
processUptime: 31117 + 335 ms
installer: com.android.packageinstaller

android.database.sqlite.SQLiteException: FullCode: 1 | ErrorCode: 1 | ExtendedErrorCode: 0 | Message: invalid fts5 file format (found 0, expected 4 or 5) - run 'rebuild' | ExtraMessage: , while compiling: UPDATE message INDEXED BY message_thread_story_parent_story_scheduled_date_latest_revision_id_index
          SET read = 1, reactions_unread = 0, reactions_last_seen = 1726591443794
          WHERE
      thread_id = ? AND
      story_type = 0 AND
      parent_story_id <= 0 AND
      latest_revision_id IS NULL AND
      (
        read = 0 OR
        (
          reactions_unread = 1 AND
          ((message.type & 31 = 21) OR (message.type & 31 = 23) OR (message.type & 31 = 22) OR (message.type & 31 = 24) OR (message.type & 31 = 25) OR (message.type & 31 = 26) OR (message.type & 31 = 2) OR (message.type & 31 = 11))
        )
      )
       AND date_received <= ?
          RETURNING _id, from_recipient_id, date_sent, type, expires_in, expire_started, thread_id, story_type
at net.zetetic.database.sqlcipher.SQLiteConnection.nativePrepareStatement(Native Method)
at net.zetetic.database.sqlcipher.SQLiteConnection.acquirePreparedStatement(SQLiteConnection.java:973)
at net.zetetic.database.sqlcipher.SQLiteConnection.prepare(SQLiteConnection.java:537)
at net.zetetic.database.sqlcipher.SQLiteSession.prepare(SQLiteSession.java:592)
at net.zetetic.database.sqlcipher.SQLiteProgram.<init>(SQLiteProgram.java:64)
at net.zetetic.database.sqlcipher.SQLiteQuery.<init>(SQLiteQuery.java:43)
at net.zetetic.database.sqlcipher.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:48)
at net.zetetic.database.sqlcipher.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1610)
at net.zetetic.database.sqlcipher.SQLiteDatabase.rawQuery(SQLiteDatabase.java:1529)
at org.thoughtcrime.securesms.database.SQLiteDatabase.lambda$rawQuery$5(SQLiteDatabase.java:353)
at org.thoughtcrime.securesms.database.SQLiteDatabase.$r8$lambda$63Fe22gM04vRs0Lck4IAEYvS3K8(SQLiteDatabase.java:0)
at org.thoughtcrime.securesms.database.SQLiteDatabase$$ExternalSyntheticLambda11.run(R8$$SyntheticClass:0)
at org.thoughtcrime.securesms.database.SQLiteDatabase.traceSql(SQLiteDatabase.java:112)
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.MessageTable.setMessagesRead(MessageTable.kt:2322)
at org.thoughtcrime.securesms.database.MessageTable.setMessagesReadSince(MessageTable.kt:2255)
at org.thoughtcrime.securesms.database.ThreadTable.setReadSince(ThreadTable.kt:535)
at org.thoughtcrime.securesms.database.ThreadTable.setReadSince(ThreadTable.kt:516)
at org.thoughtcrime.securesms.database.ThreadTable.setReadSince(ThreadTable.kt:511)
at org.thoughtcrime.securesms.conversation.MarkReadHelper.lambda$onViewsRevealed$0(MarkReadHelper.java:65)
at org.thoughtcrime.securesms.conversation.MarkReadHelper.$r8$lambda$B4EhSn6sRL5I5qd-ty8vyoMfbHo(MarkReadHelper.java:0)
at org.thoughtcrime.securesms.conversation.MarkReadHelper$$ExternalSyntheticLambda0.run(R8$$SyntheticClass:0)
at org.thoughtcrime.securesms.util.concurrent.SerialMonoLifoExecutor.lambda$enqueue$0(SerialMonoLifoExecutor.java:44)
at org.thoughtcrime.securesms.util.concurrent.SerialMonoLifoExecutor.$r8$lambda$DG-JDqK_CQzQ4r7XEovANUj-KMk(SerialMonoLifoExecutor.java:0)
at org.thoughtcrime.securesms.util.concurrent.SerialMonoLifoExecutor$$ExternalSyntheticLambda0.run(R8$$SyntheticClass:0)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
at java.lang.Thread.run(Thread.java:1012)
at org.signal.core.util.concurrent.SignalExecutors$NumberedThreadFactory$1.run(SignalExecutors.java:109)
at [[ ↑↑ Original Trace ↑↑ ]].(:0)
at [[ ↓↓ Exception Message ↓↓ ]].(:0)
at FullCode: 1 | ErrorCode: 1 | ExtendedErrorCode: 0 | Message: invalid fts5 file format (found 0, expected 4 or 5) - run 'rebuild' | ExtraMessage: , while compiling: UPDATE message INDEXED BY message_thread_story_parent_story_scheduled_date_latest_revision_id_index
          SET read = 1, reactions_unread = 0, reactions_last_seen = 1726591443794
          WHERE
      thread_id = ? AND
      story_type = 0 AND
      parent_story_id <= 0 AND
      latest_revision_id IS NULL AND
      (
        read = 0 OR
        (
          reactions_unread = 1 AND
          ((message.type & 31 = 21) OR (message.type & 31 = 23) OR (message.type & 31 = 22) OR (message.type & 31 = 24) OR (message.type & 31 = 25) OR (message.type & 31 = 26) OR (message.type & 31 = 2) OR (message.type & 31 = 11))
        )
      )
       AND date_received <= ?
          RETURNING _id, from_recipient_id, date_sent, type, expires_in, expire_started, thread_id, story_type.(:0)

Probably9857

This is a known issue, and they have a fix.

https://github.com/signalapp/Signal-Android/issues/13693

You'll need Signal 7.17.2, and then you'll still get the error one time. After that, you should be good (according to the comments on their issue).

7.17.2 is apparently still in beta though...and commenters in other issues are saying 7.17.2 still have the issue (or a different issue)...but at least they appear to be working on it.