You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is something that first came up during testing the community history archive protocol, which is why I thought the crash is related to those changes. However it turns out this crash is reproducable when there's not community history archive in play at all.
Here's how it happens:
Create a community
Create a channel
Send some messages to that channel (although, possible this isn't necessary)
Invite someone to that community
Login as that someone, join the community
Enter the channel, and click "Fetch more messages"
Notice how the stack trace says that it fails at requestMoreMessages.
This calls SyncChatFromSyncedFrom in status-go.
I tried debugging this but it's kinda hard. The moment the fetch more button is clicked the app crashes even ignoring logs.
One important note:
When restarting the app (as that invited someone) and entering the channel again, hitting the "fetch more messages" button now doesn't crash it anymore.
So this seems to be only an issue upon recent community invite...
The text was updated successfully, but these errors were encountered:
This is something that first came up during testing the community history archive protocol, which is why I thought the crash is related to those changes. However it turns out this crash is reproducable when there's not community history archive in play at all.
Here's how it happens:
The app crashes with:
Notice how the stack trace says that it fails at
requestMoreMessages
.This calls
SyncChatFromSyncedFrom
in status-go.I tried debugging this but it's kinda hard. The moment the fetch more button is clicked the app crashes even ignoring logs.
One important note:
When restarting the app (as that invited someone) and entering the channel again, hitting the "fetch more messages" button now doesn't crash it anymore.
So this seems to be only an issue upon recent community invite...
The text was updated successfully, but these errors were encountered: