C++
4.9.3 C++ Specific Changes
Fixed: starting an HTTP server will no longer fail because of invalid transport config values. (#15553) Fixed: Fixed: starting an HTTP server will now default to using port 80, as the docs suggest, when previously it would incorrectly default to port 8080. (#15553)4.9.3 Common Changes
Changed: Added more actionable information to common connection handshake issues. (#15298) Fixed: Fixed: Some Android devices could fail to export logs to the portal due to a file permissions error (#15582)No C++ Specific Changes
4.9.1 Common Changes
Fixed: iOS 18 crashes related to Bluetooth LE are now resolved. (#15351) Fixed: Disk usage stats are now reported in small peer info on android devices4.9.0 C++ Specific Changes
Added: PendingIDSpecificOperation::update_v2() which passes nullptr to the lambda if the document is not found (#14471) Added: WriteTransactionPendingIDSpecificOperation::update_v2() which passes nullptr to the lambda if the document is not found. (#14471) Changed: libditto.a is now compiled with the fPIC compiler option, to generate position-independent code (#14911) Fixed: The static Ditto::get_sdk_version() function will now return a correct result if called before the Ditto constructor. (#15072) Deprecated: PendingIDSpecificOperation::update(), whose behavior did not match the documentation. Replaced with update_v2(). (#14471) Deprecated: WriteTransactionPendingIDSpecificOperation::update(), whose behavior did not match the documentation. Replaced with update_v2(). (#14471) Removed: An incorrect error log about loading the ditto core library on Android. (#14908)4.9.0 Logging Clarity Improvements
This release comes with a number of logging clarity improvements. The goal of these changes are to make Ditto logs more consumable and actionable for end users. While there are wide ranging changes one of the principal goals of this work is to make our INFO level logs contain the right information to understand the state and health of the Ditto SDK.
-
More information is included when physical connections start and end (such as the type of connection and the remote peer’s key)
-
Devices that try to connect to themselves now say “device has connected to itself” instead of an error about the remote site ID being the same as the local peer
-
Authentication client logs have been made more human readable. In particular:
-
Recoverable errors are logged together with information about the recovery actions that are being undertaken
-
Several abbreviations have been replaced with human-readable descriptions
-
Errors are printed using their descriptions rather than by dumping debug representations
-
Abbreviated jargon has been replaced with clearer wording in various log lines
-
“phy ended” has become “physical connection ended”
-
“error getting char” has become “required Ditto BLE characteristic not found”
-
“error getting radio state” has become “error getting Windows Bluetooth radio state”
-
Peer events that represent a transport starting or stopping are now logged with the message “transport started”/”transport ended” rather than as a raw peer_event=… log
-
Reduced the noisiness of “starting” log lines around Ditto initialization time
-
Noise from long peer keys in logs has been reduced in some places by replacing them with their truncated form
-
Noise from duplicated peer ID/peer key information in replication logs has been reduced by consolidating the information
-
“starting compression and export” is now followed by a “completed export” log at the same level
-
Successful SQLite WAL recovery logs were further lowered from INFO to DEBUG