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
My Android Pixel and iPad are both logged in latest Converse (249) to cvoell.eth associated inbox Id and are in the group chat XMTP Eng 3.
Currently they are not receiving messages from other participants in the chat, but they do both see messages that I send from cvoell.eth from either device.
This is messy to diagnose because I was also testing earlier with groups that included accounts that did not have all their old installation keys removed, and with a bot that was on an old version of libxmtp.
So it is possible that this state where two installations keys from the same inbox id are in some forked state from the rest of the group, is a result of some invalid state from starting groups with accounts on older versions, etc.
Describe the bug
My Android Pixel and iPad are both logged in latest Converse (249) to cvoell.eth associated inbox Id and are in the group chat XMTP Eng 3.
Currently they are not receiving messages from other participants in the chat, but they do both see messages that I send from cvoell.eth from either device.
This is messy to diagnose because I was also testing earlier with groups that included accounts that did not have all their old installation keys removed, and with a bot that was on an old version of libxmtp.
So it is possible that this state where two installations keys from the same inbox id are in some forked state from the rest of the group, is a result of some invalid state from starting groups with accounts on older versions, etc.
Before I try and repro with new accounts, I just wanted to capture logs and screen shots here of the current state.
cameron-android-libxmtp-logs.log
cvoell.ios-libxmtp.logs.txt
Expected behavior
No response
Steps to reproduce the bug
No response
The text was updated successfully, but these errors were encountered: