Releases: xmtp/xmtp-react-native
v4.3.3
v4.3.2
v4.3.1
v4.3.0
This release introduces several enhancements, including quantum-resistant encryption, improved identity management, and refined read/write rate limits.
If you've been building on a previous release, this one should be a drop-in replacement. Update as soon as possible to take advantage of these enhancements and fixes.
Support for quantum-resistant encryption
XMTP now supports quantum-resistant encryption, providing enhanced security for message transmission and storage. This upgrade ensures your app is protected against future quantum computer attacks through post-quantum cryptography.
To learn more, see Quantum resistance.
Stream failure callbacks for mobile
Added optional onClose callback parameters to all streaming methods. These callback parameters are triggered when streams fail, enabling you to implement automatic retry logic and graceful error recovery. This enables apps to automatically restart failed streams with configurable retry intervals and maximum retry attempts.
To learn more, see Handle failed streams.
Consistent identity ordering
When an inbox has multiple associated identities, the identities array is now ordered by the client_timestamp_ns field, which sorts identities based on when they were added to the inbox, placing the earliest added identity first.
To learn more, see Select the identity to display.
Enhanced rate limits with separate read/write limits
XMTP now provides separate rate limits for read and write operations, offering more granular control over API usage. Read operations are limited to 20,000 requests per 5-minute window, while write operations are limited to 3,000 messages per 5-minute window.
To learn more, see Observe rate limits.
Improved history sync
History sync has been enhanced with better consent management across installations and improved handling of denied conversations. These changes ensure a more consistent experience when users access XMTP from multiple installations.
To learn more, see Enable history sync.
Enhanced group chat updates
Group membership changes now automatically trigger group update codec messages, ensuring all participants receive consistent information about group state changes. This improves the reliability of group chat synchronization across all devices.
To learn more, see Manage group chat membership.
Performance improvements and bug fixes
This release includes various performance optimizations throughout the SDK, resulting in faster message processing, improved memory usage, and better overall responsiveness. The release also includes bug fixes that improve the reliability of group chats and address a performance degradation issue that could occur when creating new groups.
To learn more about optimizing your XMTP implementation, see Debug your app.
v4.2.7
v4.2.6
v4.2.5
v4.2.4
This patch introduces several targeted enhancements and clarifications related to managing client builds, network statistics, installations, and group chats.
If you’ve been building on a previous release, this one should be a drop-in replacement. Update as soon as possible to take advantage of these enhancements and fixes.
Automatic offline client builds when an inboxId is present
When building a client with an existing inboxId, the client automatically operates in offline mode, as no network request is required to check the identity ledger. In offline mode, the client:
- Skips all network requests (preference syncing between installations, validating inbox, etc.)
- Works entirely from the local database
- Can be synchronized later with
syncAllConversations()or by recreating the client without the offline flag.
To learn more, see Build an existing client.
Reset network statistics for debugging
A new helper, clearAllStatistics(), lets you reset all API/identity/stream network statistics counters.
Use it to get a clean baseline between test runs or free memory on devices where cached gRPC stats grow over time.
To learn more, see Network statistics.
Support installation limits and more robust support for revocations
XMTP now enforces up to 5 app installations per inbox ID.
When the installation limit is reached, you can enable users to revoke one or more installations to free up a slot. Users can also revoke installations without needing to log in, using only their recovery address signer to authorize the revocation. This feature is particularly useful when users have reached the 5-installation limit and need to free up space for new installations without having access to the installations they want to revoke.
To learn more, see Revoke installations.
Support slightly larger group chats
The maximum group chat size has been raised from 220 to 250 members.
To learn more, see Create a new group chat.
Reduced risk of group chat forks
Additional safeguards have been added to minimize the chance of unintended group chat forks.
To learn about what group chat forks are and how they can occur, see MLS Group State Forks: What, Why, How