Allows you to specify a specifc port that can will be used for mDNS announcements and connections on a given device. This can be used for connect with peers across a VLAN while scanning for open ports.

Not setting the config will result in the current default behavior of a random port being assigned.



Setting the config

The config can be set using DQL ALTER SYSTEM and the tcp_server_bind_mdns_server_port config.

This command should be run using the ditto.store.execute(...) command within your application.



Resolves a race condition that could be hit when closing a sync subscription or stopping sync that caused Ditto to crash.

To support scenarios with cross-VLAN device discovery we increated the TTL to ensure message have enough time to reach their destination and get acknowledged.

This fix addresses the issue causing a Live Query callback to receive a delta update, known as a diff, before the initial document.

Previously, there was an issue in which two documents on different internal versions could fail to integrate changes created using an older CRDT version.

Due to a race condition caused by the logging system mistakenly identifying the previous transaction as blocking the current one, the logger would inaccurately indicate the current transaction as being blocked by the previous one from an unknown originator.

This issue was due to an aging dependency with a race condition, which caused thread tasks to get stuck and transactions to be blocked for extended periods.

We've optimized compilation by reducing the size of each binary slice of the Ditto SDKs by 19% and fixing incompatibility with PLCrashReporter.

This new system parameter allows greater control over the use of Bluetooth Low Energy (LE) connections in Ditto's peer-to-peer mesh network. When set to false, Ditto creates Bluetooth LE connections alongside other peer-to-peer connections, serving as a fallback if the primary transport, such as Apple Wireless Direct Link (AWDL) or LAN, fails.

However, before you enable the mesh_chooser_avoid_redundant_bluetooth parameter, consider the following technical tradeoffs:

To enable the mesh_chooser_avoid_redundant_bluetooth parameter, use the following DQL query:

This allows peers with large permission sets to more quickly establish connections on low bandwidth transports like Bluetooth LE.

Before, if you invoked an empty POST request, the cloud load balancer would reject your request with a 411 - Length Required error message.

Now you must explicitly state that the body of your POST request is empty by setting content-length: 0 in the header of your HTTP API call.

There was an issue where invoking subscribe() on an invalid query caused sync to be silently disabled.

Invalid queries in the subscribe() method are now identified, disabled, and logged as errors.

In scenarios where subscriptions rapidly changed back and forth while documents were being concurrently altered, documents would diverge at merge.

We’ve removed subscription logic ignoring acknowledgements based on assumed subscription mismatch and introduced salting functionality to ensure each document is unique for each occurrence of a subscription. This helps differentiate between new and reverted subscription states.

To eliminate redundant data from being synced unnecessarily, regardless of whether the remote peer previously acknowledged them, we’ve added validation checks ensuring that only unacknowledged data is synced.

This fix reduces sync update file sizes, leading to more performant session sync updates, particularly in apps consisting of large, stable subscriptions and infrequent document changes.

Before this fix, iOS and Mac randomly failed to authenticate against a WebHook provider with an error traced to the provider NSString not being kept alive for the duration of the login request, leading to authentication failure and resulting in an error message stating "no auth config set up."

The fix involved guaranteeing that the provider NSString persists for the duration of the dispatched login request, preventing premature deallocation of the string.

After upgrading to version 4.7 of the SDK, you may notice unexpected errors while using the legacy query builder language. These errors are likely due to invalid field names or path expressions previously undetected.

In addition, make sure to start unquoted_string with an underscore (_), a letter, or an alphanumeric character. For example, the following equivalent regular expression: [A-Za-z_][A-Za-z0-9_]*.

For specific examples, see Query Syntax (Legacy) > Field Path Navigation.

Before this improvement, concurrent write transactions were long-lived, potentially causing deadlocks and request timeouts. Now you'll experience more effective handling of multiple attachments being processed at the same time.

With the latest release, Ditto handles unexpected situations or errors in a way that allows it to recover and continue functioning without crashing or causing disruptions.

This rollout includes new system parameters for the MeshChooser feature for configuring a limited set of variables, allowing you to adjust certain settings during runtime.

The warning message previously logged when peers connected within the mesh is no longer recorded or printed.

Previously, when syncing in mixed mesh environments from Ditto SDK version 4.0.0 of the SDK to version 3.0.0, only partial updates were transmitted. With this release, all updates are transmitted, resulting in greater data consistency and completeness when syncing across different versions of the SDK.

Previously, the Small Peer Info collector would become stuck when attempting to upload logs in certain situations. Since resolving this issue, the Small Peer Info collector functions properly in those conditions.

With this fix, operations related to fetching attachments function as expected.

When using SystemParameter to configure timeouts before this fix, if using different types to encode the values representing the timeout, for instance, Milliseconds and Seconds, the values failed to downcast, an error log printed, and the new value ignored.

Now, when using mismatched wrapper types, Ditto performs a compatibility check, validates, and, if needed, converts them as appropriate.

We've added a warning message that logs when the deviceName property is set after the sync process has started.

Previously, setting deviceName of a Ditto instance after starting sync did not trigger a warning.

This new message warns you that the new value you've set only takes effect after you've restarted the sync process in your app.

Due to an issue in the TransportConfig, the retry connection interval was incorrectly set in seconds instead of milliseconds.

This fix corrects the interval to properly use milliseconds instead of seconds.