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
When using the XMTP browser-sdk, we noticed an inconsistency between the objects returned by getDmByInboxId and those returned by list(). Specifically, getDmByInboxId does not return Conversation objects that include the dmPeerInboxId method, whereas objects from list() do. This behavior causes issues when trying to use the dmPeerInboxId method on conversations fetched by getDmByInboxId.
Expected behavior
Both methods (list() and getDmByInboxId) should return Conversation objects with the same structure, including the dmPeerInboxId method.
Steps to reproduce the bug
Use xmtpClient.conversations.list() to fetch all conversations.
Verify that the returned objects have the dmPeerInboxId method.
Use xmtpClient.conversations.getDmByInboxId(inboxId) with a valid inbox ID.
Check the returned object for the dmPeerInboxId method.
The text was updated successfully, but these errors were encountered:
Describe the bug
When using the XMTP browser-sdk, we noticed an inconsistency between the objects returned by getDmByInboxId and those returned by list(). Specifically, getDmByInboxId does not return Conversation objects that include the dmPeerInboxId method, whereas objects from list() do. This behavior causes issues when trying to use the dmPeerInboxId method on conversations fetched by getDmByInboxId.
Expected behavior
Both methods (list() and getDmByInboxId) should return Conversation objects with the same structure, including the dmPeerInboxId method.
Steps to reproduce the bug
The text was updated successfully, but these errors were encountered: