Release Notes
Swift

﻿
4.8.1 Version Release
Release Date: Sept 5, 2024
4.8.1 Swift Specific Changes
🛠️Fixed: An issue where iOS devices may fail to sync on LAN when the app goes in the backgrounded then back to the foregrounded. (#14150)
🛠️ Fixed: An issue with AWDL where Ditto would create invalid connection advertisements when app is backgrounded and foregrounded, affecting mesh connectivity (#14151)
﻿
4.8.0 Version Release
Release Date: Aug 28, 2024
The version 4.8.0 SDK release update brings a substantial number of improvements and new features designed to enhance your development experience and provide even more powerful tools for building robust, real-time applications.
﻿
4.8.0 Swift Specific Changes
⭐️ ➕ Added: Mac Catalyst platform support #13051
⭐️ ➕ Added: tvOS platform support #13049
⭐️ ➕ Added: method export(to:) to DittoLogger, which exports collected logs to a compressed and JSON-encoded file on the local file system.  Logs returned through this method are at DEBUG log level. This new API can be used to do forensic log gathering on a device. Logs are always collected and restricted to a fixed specific size limit to ensure they don't grow endlessly. Once the size limit has reached new logs replace the oldest logs. #11961
➕ Added: Properties peerKeyString1 and peerKeyString2 on DittoConnection replacing the deprecated properties peer1 and peer2  #12799
➕ Added: Documentation for startSync() and disableSyncWithV3() to include a recommendation for performance improvement. #13098
Performance of initial sync when bootstrapping a new peer can be improved by calling disableSyncWithV3() before calling startSync(). 

Only do this when all peers in the mesh are known to be running Ditto v4 or higher.
➕ Added: Documentation for property peerMetadata on DittoPeer to add information about how the property behaves over the lifecycle of the DittoPresenceGraph #13479
﻿
⚠️ Deprecated: Properties peer1 and peer2 on DittoConnection, please use peerKeyString1 and peerKeyString2 instead #12799
⚠️ Deprecated: Property queryOverlapGroup on DittoPeer and DittoRemotePeerV2, always return 0 going forward. Query Overlap Groups was an experiemental feature that has been removed after it was determined this would not support production scenarios.
﻿
❗️🗑️ Removed (Experimental): property queryOverlapGroup of DittoExperimental
❗️🗑️ Removed (Experimental): methods priority(forQueryOverlapGroup:) and setPriority(_:forQueryOverlapGroup:) of DittoExperimental
❗️🗑️ Removed: (Experimental) deprecated methods setQueryOverlapGroup(queryOverlapGroup:) and setPriority(_:forQueryOverlapGroup:ditto:) of DittoExperimental
﻿
﻿
Updated 24 Sep 2024
Did this page help you?
Directory of Release Notes
Kotlin