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
After cleaning up multiple unused installations for better testing, attempting to sync or send a message in an existing conversation on xmtp.chat using [email protected] now throws an "Intent not committed" error. The console logs show multiple xmtp_mls::groups::mls_sync errors such as:
Expected behavior
Messages should send and sync normally without the "Intent not committed" error, regardless of how many installations have been removed or cleaned up.
Steps to reproduce the bug
Clean or remove multiple unused installations for testing purposes.
Open xmtp.chat (current version for @xmtp/browser-sdk is 0.0.21).
Attempt to sync or open an existing conversation.
Send a message in that conversation.
Observe the "Intent not committed" error and related logs in the console.
The text was updated successfully, but these errors were encountered:
@anthony23991, after removing installations, you may need to also remove the associated databases. in the browser, you'll need an extension to browse the OPFS and remove them manually.
please let me know if these issues persist after removing the database.
Describe the bug
After cleaning up multiple unused installations for better testing, attempting to sync or send a message in an existing conversation on xmtp.chat using
[email protected]
now throws an "Intent not committed" error. The console logs show multiplexmtp_mls::groups::mls_sync
errors such as:Expected behavior
Messages should send and sync normally without the "Intent not committed" error, regardless of how many installations have been removed or cleaned up.
Steps to reproduce the bug
The text was updated successfully, but these errors were encountered: