Skip to content
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

Signal crashing after transfer/restore #13740

Open
3 tasks done
mheck-lm opened this issue Oct 21, 2024 · 1 comment
Open
3 tasks done

Signal crashing after transfer/restore #13740

mheck-lm opened this issue Oct 21, 2024 · 1 comment

Comments

@mheck-lm
Copy link

Guidelines

  • I have searched searched open and closed issues for duplicates
  • I am submitting a bug report for existing functionality that does not work as intended
  • This isn't a feature request or a discussion topic

Bug description

After Transferring or Restoring from a backup the app asks for confirmation of the phone number but then crashes after confirming the PIN.
Any attempts of opening the app after that crash lead to another crash.
adb logcat outputs:

10-21 10:57:20.061  7440 13079 E AndroidRuntime: Process: org.thoughtcrime.securesms, PID: 7440
10-21 10:57:20.061  7440 13079 E AndroidRuntime: org.thoughtcrime.securesms.database.RecipientTable$MissingRecipientException: Failed to find recipient with ID: RecipientId::3245
10-21 10:57:20.061  7440 13079 E AndroidRuntime:        at org.thoughtcrime.securesms.database.RecipientTable.findRemappedIdRecord(RecipientTable.kt:759)
10-21 10:57:20.061  7440 13079 E AndroidRuntime:        at org.thoughtcrime.securesms.database.RecipientTable.getRecord(RecipientTable.kt:747)
10-21 10:57:20.061  7440 13079 E AndroidRuntime:        at org.thoughtcrime.securesms.recipients.LiveRecipient.fetchAndCacheRecipientFromDisk(LiveRecipient.java:192)
10-21 10:57:20.061  7440 13079 E AndroidRuntime:        at org.thoughtcrime.securesms.recipients.LiveRecipient.resolve(LiveRecipient.java:152)
10-21 10:57:20.061  7440 13079 E AndroidRuntime:        at org.thoughtcrime.securesms.recipients.Recipient$Companion.resolved(Recipient.kt:837)
10-21 10:57:20.061  7440 13079 E AndroidRuntime:        at org.thoughtcrime.securesms.recipients.Recipient$Companion.resolvedList(Recipient.kt:843)
10-21 10:57:20.061  7440 13079 E AndroidRuntime:        at org.thoughtcrime.securesms.recipients.Recipient.resolvedList(Recipient.kt:0)
10-21 10:57:20.061  7440 13079 E AndroidRuntime:        at org.thoughtcrime.securesms.conversationlist.ConversationListDataSource.load(ConversationListDataSource.java:103)

Screenshots

No response

Device

Samsung Galaxy A55

Android version

14

Signal version

7.19.2

Link to debug log

No response

@mheck-lm
Copy link
Author

We found the following entries in the Debug log:

10-24 14:34:08.086 14901  9853 W RecipientTable: Missing recipient for RecipientId::3245, but found it in the remapped records as RecipientId::3256
10-24 14:34:08.086 14901  9851 W RecipientTable: Missing recipient for RecipientId::3245, but found it in the remapped records as RecipientId::3256

With further search we found two chats that contained "strange" contents:

  1. There was a "Message request" message displayed beneath a name, but within the chat was none visible only a few "safety number changed" messages
  2. Nothing was displayed beneath a name but in the chat was something around "updating the contact because it has changed"

⇒ After deleting both these chats we were able to migrate to the new phone successfully!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant