Changelog

• DittoLogger class added, which allows extra logging functionality through setCustomLogCallback and setLogFile/setLogFileURL.
• CFBundleShortVersionString in the framework's Info.plist now only contains alphanumeric characters, which should resolve any issues with submitting apps to TestFlight or the App Store.

pod 'DittoSyncKitSwift', '=1.0.0-alpha7'

pod 'DittoSyncKit', '=1.0.0-alpha7'

• Performance and stability improvements.
• Fix default data insertion such that merge semantics are consistent and duplicate data isn't created.

pod 'DittoSyncKitSwift', '=1.0.0-alpha6'

pod 'DittoSyncKit', '=1.0.0-alpha6'

• Added a new intermediate security identity for a shared secret key. This is a simplistic authentication mode which is normally only suitable for private apps where all the users and devices are trusted.
• Fixed an issue that prevented Counter values from syncing correctly
• Renamed DittoAttachmentStatus to DittoAttachmentFetchEvent and subsequently Incomplete status to Progre ss.

pod 'DittoSyncKitSwift', '=1.0.0-alpha5'

pod 'DittoSyncKit', '=1.0.0-alpha5'

• Fix issue where attachments could stop being fetched incorrectly.

pod 'DittoSyncKitSwift', '=1.0.0-alpha4'

pod 'DittoSyncKit', '=1.0.0-alpha4'

• Added new observeWithNextSignal API to allow the application to control the delivery of the next observe callback event.
• Fixed several issues related to attachments that could delay sync.
• Simplified log statements

pod 'DittoSyncKitSwift', '=1.0.0-alpha3'

pod 'DittoSyncKit', '=1.0.0-alpha3'

• Note that this is a release with breaking changes and clients using releases in the 1.0 series will not be able to communicate with clients running a version that is anything less than 1.0. This should hopefully not be an issue because this release of the SDK has changed the name to be DittoSyncKitSwift as opposed to DittoKitSwift.
• Lots of performance improvements and some bug fixes.

pod 'DittoSyncKitSwift', '=1.0.0-alpha1'

pod 'DittoSyncKit', '=1.0.0-alpha1'

• Note that this is a release with breaking changes, even just in terms of clients running 0.4.0 not being able to communicate with clients running 0.3.X releases.
• Fixes for memory leaks.
• Performance improvements.

pod 'DittoSyncKitSwift', '=0.4.0-alpha1'

pod 'DittoSyncKit', '=0.4.0-alpha1'

• Fixed an issue where inserting data as default data (setting the isDefault parameter to true) could lead to data that would not merge as expected.

pod 'DittoSyncKitSwift', '=0.3.5'

pod 'DittoSyncKit', '=0.3.5'

• Fixed a bug with query compilation where integer literals in the query would lead to a query compilation failure.

pod 'DittoSyncKitSwift', '=0.3.4'

pod 'DittoSyncKit', '=0.3.4'

• Improved LAN background sync for iOS apps

pod 'DittoSyncKitSwift', '=0.3.3'

pod 'DittoSyncKit', '=0.3.3'

• Fixes a memory leak in the Cocoa SDK when using findByID() to query documents.

pod 'DittoSyncKitSwift', '=0.3.2'

pod 'DittoSyncKit', '=0.3.2'

• Added a new LAN transport mode WiFiFixedPort to listen for connections on a known port.
• DittoKit has a new sdkVersion property describing which build of DittoKit is installed. Please include this information in support requests.
• Fixed bug where an attachment transfer may not resume after being interrupted.
• Fixed bug where a long-lasting Bluetooth connection may spontaneously disconnect and reconnect.
• Improvements to reconnection speed.

pod 'DittoSyncKitSwift', '=0.3.1'

pod 'DittoSyncKit', '=0.3.1'

• DITLogger class added, which allows extra logging functionality through setCustomLogCallback and setLogFile/setLogFileURL.
• CFBundleShortVersionString in the framework's Info.plist now only contains alphanumeric characters, which should resolve any issues with submitting apps to TestFlight or the App Store.

pod 'DittoSyncKitSwift', '=1.0.0-alpha7'

pod 'DittoSyncKit', '=1.0.0-alpha7'

• Performance and stability improvements.
• Fix default data insertion such that merge semantics are consistent and duplicate data isn't created.

pod 'DittoSyncKitSwift', '=1.0.0-alpha6'

pod 'DittoSyncKit', '=1.0.0-alpha6'

• Added a new intermediate security identity for a shared secret key. This is a simplistic authentication mode which is normally only suitable for private apps where all the users and devices are trusted.
• Fixed an issue that prevented Counter values from syncing correctly
• Renamed DittoAttachmentStatus to DittoAttachmentFetchEvent and subsequently Incomplete status to Progress.

pod 'DittoSyncKitSwift', '=1.0.0-alpha5'

pod 'DittoSyncKit', '=1.0.0-alpha5'

• Fix issue where attachments could stop being fetched incorrectly.

pod 'DittoSyncKitSwift', '=1.0.0-alpha4'

pod 'DittoSyncKit', '=1.0.0-alpha4'

• Added new observeWithNextSignal API to allow the application to control the delivery of the next observe callback event.
• Fixed several issues related to attachments that could delay sync.
• Simplified log statements

pod 'DittoSyncKitSwift', '=1.0.0-alpha3'

pod 'DittoSyncKit', '=1.0.0-alpha3'

• Note that this is a release with breaking changes and clients using releases in the 1.0 series will not be able to communicate with clients running a version that is anything less than 1.0. This should hopefully not be an issue because this release of the SDK has changed the name to be DittoSyncKit as opposed to DittoKit.
• Lots of performance improvements and some bug fixes.

pod 'DittoSyncKitSwift', '=1.0.0-alpha1'

pod 'DittoSyncKit', '=1.0.0-alpha1'

• This release is not compatible with any previous SDK releases. There are a number of breaking changes both in terms of the SDK API and in terms of the internal systems used by the SDK to perform operations such as synchronization. If you have previously made use of the Ditto SDK and wish to update to this version then note that you will need to delete all existing Ditto data otherwise you will run into errors. If you have existing data that you need to keep then please contact us and we can advise you as to how you can migrate your data.
• The most notable API breaking changes are:
  • Document IDs are no longer restricted to just strings. You can now create a document ID that is a string, integer, boolean, array, map, or null. This means that when making findByID or insert calls you now need to provide a DittoDocumentID object rather than a string. Similarly, when you access a document's ID it will now return a DittoDocumentID object instead of a string.
  • The start() and stop() functions on the Ditto object have been renamed to startSync() and stopSync() respectively. They now also don't accept any arguments. If you wish to specify which transports you would like the Ditto SDK to make use of (along with any configuration that they might require) you now need to use the setTransportConfig function on the Ditto object, and pass to that a transport config object. The default transports that will be enabled are still the same as they were in previous releases of the SDK though, so if you have no custom requirements then you can simply change your start() call to startSync().
• Lots of performance improvements and bug fixes.

pod 'DittoSyncKitSwift', '=1.0.0'

pod 'DittoSyncKit', '=1.0.0'

• Fixed a bug where mDNS advertising may continue after Ditto is stopped.
• Fixed a hang that could occur creating an attachment fetcher while requesting many attachments at once.
• Fixed sync failure when there are multiple overlapping subscriptions or live queries with the same query string for the same collection.
• Fixed a potential crash and other sync failures that could occur under certain conditions.

pod 'DittoSyncKitSwift', '=1.0.0-alpha9'

pod 'DittoSyncKit', '=1.0.0-alpha9'

• Site IDs, which make up part of a Ditto identity object, are now unsigned, 64-bit integers instead of unsigned 32-bit integers.
• Fix a crash that could occur if an offset with a value greater than the number of matching documents was provided.
• Fix a potential crash that would occur if a live query had stop called on it immediately after it was created.

pod 'DittoSyncKitSwift', '=1.0.0-alpha8'

pod 'DittoSyncKit', '=1.0.0-alpha8'

• This release is not compatible with any previous SDK releases. There are a number of breaking changes both in terms of the SDK API and in terms of the internal systems used by the SDK to perform operations such as synchronization. If you have previously made use of the Ditto SDK and wish to update to this version then note that you will need to delete all existing Ditto data otherwise you will run into errors. If you have existing data that you need to keep then please contact us and we can advise you as to how you can migrate your data.
• The most notable API breaking changes are:
  • Document IDs are no longer restricted to just strings. You can now create a document ID that is a string, integer, boolean, array, map, or null. This means that when making findByID or insert calls you now need to provide a DITDocumentID object rather than a string. Similarly, when you access a document's ID it will now return a DITDocumentID object instead of a string.
  • The start() and stop() functions on the Ditto object have been renamed to startSync() and stopSync() respectively. They now also don't accept any arguments. If you wish to specify which transports you would like the Ditto SDK to make use of (along with any configuration that they might require) you now need to use the setTransportConfig function on the Ditto object, and pass to that a transport config object. The default transports that will be enabled are still the same as they were in previous releases of the SDK though, so if you have no custom requirements then you can simply change your start() call to startSync().
• Lots of performance improvements and bug fixes.

pod 'DittoSyncKitSwift', '=1.0.0'

pod 'DittoSyncKit', '=1.0.0'

• Fixed a bug where mDNS advertising may continue after Ditto is stopped.
• Fixed a hang that could occur creating an attachment fetcher while requesting many attachments at once.
• Fixed sync failure when there are multiple overlapping subscriptions or live queries with the same query string for the same collection.
• Fixed a potential crash and other sync failures that could occur under certain conditions.

pod 'DittoSyncKitSwift', '=1.0.0-alpha9'

pod 'DittoSyncKit', '=1.0.0-alpha9'

• Site IDs, which make up part of a Ditto identity object, are now unsigned, 64-bit integers instead of unsigned 32-bit integers.
• Fix a crash that could occur if an offset with a value greater than the number of matching documents was provided.
• Fix a potential crash that would occur if a live query had stop called on it immediately after it was created.

pod 'DittoSyncKitSwift', '=1.0.0-alpha8'

pod 'DittoSyncKit', '=1.0.0-alpha8'

• Note that this is a release with breaking changes, even just in terms of clients running 0.4.0 not being able to communicate with clients running 0.3.X releases.
• Fixes for memory leaks.
• Performance improvements.

pod 'DittoSyncKitSwift', '=0.4.0-alpha1'

pod 'DittoSyncKit', '=0.4.0-alpha1'

• Fixed an issue where inserting data as default data (setting the isDefault parameter to true) could lead to data that would not merge as expected.

pod 'DittoSyncKitSwift', '=0.3.5'

pod 'DittoSyncKit', '=0.3.5'

• Fixed a bug with query compilation where integer literals in the query would lead to a query compilation failure.

pod 'DittoSyncKitSwift', '=0.3.4'

pod 'DittoSyncKit', '=0.3.4'

• Improved LAN background sync for iOS apps

pod 'DittoSyncKitSwift', '=0.3.3'

pod 'DittoSyncKit', '=0.3.3'

• Fixes a memory leak in the Cocoa SDK when using findByID() to query documents.

pod 'DittoSyncKitSwift', '=0.3.2'

pod 'DittoSyncKit', '=0.3.2'

• Added a new LAN transport mode WiFiFixedPort to listen for connections on a known port.
• DittoKit has a new sdkVersion property describing which build of DittoKit is installed. Please include this information in support requests.
• Fixed bug where an attachment transfer may not resume after being interrupted.
• Fixed bug where a long-lasting Bluetooth connection may spontaneously disconnect and reconnect.
• Improvements to reconnection speed.

pod 'DittoSyncKitSwift', '=0.3.1'

pod 'DittoSyncKit', '=0.3.1'

• DittoKit 0.3 includes incompatible changes to data storage and networking - please uninstall all apps based on DittoKit 0.2 first
• The CocoaPod “DittoKit” is now Objective-C. The Swift version is published as “DittoKitSwift”. To continue working with Ditto in Swift, update your Podfile and import statement
• Support for attaching large binary files to documents and syncing them on demand
• Many SDK functions no longer throw exceptions and the “try” operator is no longer needed
• When creating documents you can no longer specify the id by providing an _id key. Instead you must specify an id as an extra argument to the insert function, if you want to explicitly set a document’s id
• A document’s id property is now id rather than _id
• The parameters for a live query callback have changed
• The sort order for a query is now controlled by an ascending/descending enum
• Faster sync performance
• Ability to connect to a peer at a known address using the Server transport type
• You can set your Ditto license key by configuring “DittoAccessLicense” in Info.plist

pod 'DittoSyncKitSwift', '=0.3.0'

pod 'DittoSyncKit', '=0.3.0'

• Faster Bluetooth sync between iOS devices when reopening app from background

pod 'DittoSyncKitSwift', '=0.2.2'

pod 'DittoSyncKit', '=0.2.2'

• Fixes a crash that can occur when calling stop().

pod 'DittoSyncKitSwift', '=0.2.1'

pod 'DittoSyncKit', '=0.2.1'

• iOS: New function observePeers() to monitor connections to other Ditto devices
• Improved query results performance
• Fixed two bugs that could lead to a crash
• Many networking improvements to speed up sync on iOS and Android

Note: SyncKit 0.2 is incompatible with version 0.1.

pod 'DittoSyncKitSwift', '=0.2.0'

pod 'DittoSyncKit', '=0.2.0'

• Fixed Bluetooth LE issue specific to older iOS devices (iPhone 6, iPad Mini 4) where sync can fail after the device is locked

pod 'DittoSyncKitSwift', '=0.1.9'

pod 'DittoSyncKit', '=0.1.9'

• Fixed Bluetooth Low Energy issue on iOS where sync may never complete, particularly with multiple devices
• Cocoa SDK detects when WiFi is disabled
• Significant performance improvements in synchronization processing

pod 'DittoSyncKitSwift', '=0.1.8'

pod 'DittoSyncKit', '=0.1.8'

• Various Bluetooth Low Energy related fixes to make Bluetooth-based communication more reliable.
• Accessing a collection using the collection function on DittoStore is no longer a throwing call and the name parameter has been removed.
• Accessing a collection can now be done by using a subscript on DittoStore, e.g. store["my-collection"].
• Live query and transport condition updates are now delivered on the main queue by default. You can specify different queues to be used if required.
• Adds queriesHash and queriesHashMnemonic to DittoStore, which allow you to get either a numberc hash or string-based mnemonic representation of a client's state in relation to the specified queries.
• Fixes a DittoDocument-related memory leak.

pod 'DittoSyncKitSwift', '=0.1.7'

pod 'DittoSyncKit', '=0.1.7'

• The full SDK API is now usable from Objective-C. Some classes that couldn't be represented in Objective-C have counterparts with an ObjC suffix

pod 'DittoSyncKitSwift', '=0.1.6'

pod 'DittoSyncKit', '=0.1.6'

• Improved handling of retrieving numeric fields from documents
• mDNS/AWDL now correctly filters remote peers by app name
• Single document update operation closures now have the document as an optional parameter

pod 'DittoSyncKitSwift', '=0.1.5'

pod 'DittoSyncKit', '=0.1.5'

• Synchronized version bump release

implementation "live.ditto:dittosynckit:1.0.0-alpha7"

• Performance and stability improvements.
• Fix default data insertion such that merge semantics are consistent and duplicate data isn't created.

implementation "live.ditto:dittosynckit:1.0.0-alpha6"

• Added a new intermediate security identity for a shared secret key. This is a simplistic authentication mode which is normally only suitable for private apps where all the users and devices are trusted.
• Fixed an issue that prevented Counter values from syncing correctly
• Renamed DittoAttachmentStatus to DittoAttachmentFetchEvent and subsequently Incomplete status to Progre ss.

implementation "live.ditto:dittosynckit:1.0.0-alpha5"

• Fix issue where attachments could stop being fetched incorrectly.

implementation "live.ditto:dittosynckit:1.0.0-alpha4"

• Added new observeWithNextSignal API to allow the application to control the delivery of the next observe callback ev ent.
• Fixed several issues related to attachments that could delay sync.
• Simplified log statements

implementation "live.ditto:dittosynckit:1.0.0-alpha3"

• Decreases the file size of the AAR

implementation "live.ditto:dittosynckit:1.0.0-alpha2"

• Note that this is a release with breaking changes and clients using releases in the 1.0 series will not be able to communicate with clients running a version that is anything less than 1.0. This should hopefully not be an issue because this release of the SDK has changed the name to be DittoSyncKit as opposed to DittoKit.
• Lots of performance improvements and some bug fixes.

implementation "live.ditto:dittosynckit:1.0.0-alpha1"

• Fixed an issue where extensive writes can cause a session time-out

implementation "live.ditto:dittokit:0.4.0-alpha6"

• Fixed finalizer logic with the following types:
  • DittoAttachment
  • DittoAttachmentFetcher
  • DittoKit
  • DittoLiveQuery
  • DittoSubscription

implementation "live.ditto:dittokit:0.4.0-alpha5"

• Fixes an issue where deletes might not propagate correctly in a multi-hop mesh

implementation "live.ditto:dittokit:0.4.0-alpha4"

• Fixed an error where presence data was failing to be deserialized properly.

implementation "live.ditto:dittokit:0.4.0-alpha3"

From the 0.4.0-alpha1 release notes:

• Note that this is a release with breaking changes, even just in terms of clients running 0.4.0 not being able to communicate with clients running 0.3.X releases.
• Fixes for memory leaks.
• Performance improvements.

implementation "live.ditto:dittokit:0.4.0-alpha2"

• Note that this is a release with breaking changes, even just in terms of clients running 0.4.0 not being able to communicate with clients running 0.3.X releases.
• Fixes for memory leaks.
• Performance improvements.

implementation "live.ditto:dittokit:0.4.0-alpha1"

• Fixed an issue where inserting data as default data (setting the isDefault parameter to true) could lead to data that would not merge as expected.

implementation "live.ditto:dittokit:0.3.5"

• Fixed a bug with query compilation where integer literals in the query would lead to a query compilation failure.

implementation "live.ditto:dittokit:0.3.4"

• Android-specific performance improvements for large collections
• Java: DittoDocument's "value" field has been replaced with "getValue()"

implementation "live.ditto:dittokit:0.3.3"

• Fixes bug where Android phones sometimes do not activate Bluetooth if it is enabled after launching the app

implementation "live.ditto:dittokit:0.3.2"

• Added a new LAN transport mode WiFiFixedPort to listen for connections on a known port.
• Android phones using the Bluetooth transport will no longer change their device name.
• DittoKit has a new sdkVersion property describing which build of DittoKit is installed. Please include this information in support requests.
• Fixed bug where an attachment transfer may not resume after being interrupted.
• Fixed bug where a long-lasting Bluetooth connection may spontaneously disconnect and reconnect.
• Improvements to reconnection speed.

implementation "live.ditto:dittokit:0.3.1"

• DittoKit 0.3 includes incompatible changes to data storage and networking - please uninstall all apps based on DittoKit 0.2 first
• Support for attaching large binary files to documents and syncing them on demand
• When creating documents you can no longer specify the id by providing an _id key. Instead you must specify an id as an extra argument to the insert function, if you want to explicitly set a document’s id
• A document’s id property is now id rather than _id
• The parameters for a live query callback have changed
• The sort order for a query is now controlled by an ascending/descending enum
• Fixed crash when inserting large amounts of data into a document
• Faster sync performance
• Ability to connect to a peer at a known address using the Server transport type

implementation "live.ditto:dittokit:0.3.0"

• Fixed an issue where DittoKit would not work in 32-bit contexts.

implementation "live.ditto:dittokit:0.2.3"

• Reduced minimum Android SDK API level from 26 to 25 to support Android 7.1 devices.

implementation "live.ditto:dittokit:0.2.2"

• Fixes a crash that can occur when calling stop().

implementation "live.ditto:dittokit:0.2.1"

• Improved query results performance
• Fixed two bugs that could lead to a crash
• Many networking improvements to speed up sync on iOS and Android

Note: SyncKit 0.2 is incompatible with version 0.1.

implementation "live.ditto:dittokit:0.2.0"

• Improved handling of retrieving numeric fields from documents
• Fixes a bug where observe would not create a subscription

implementation "live.ditto:dittokit:0.1.3"

• This release is not compatible with any previous SDK releases. There are a number of breaking changes both in terms of the SDK API and in terms of the internal systems used by the SDK to perform operations such as synchronization. If you have previously made use of the Ditto SDK and wish to update to this version then note that you will need to delete all existing Ditto data otherwise you will run into errors. If you have existing data that you need to keep then please contact us and we can advise you as to how you can migrate your data.
• The most notable API breaking changes are:
  • Document IDs are no longer restricted to just strings. You can now create a document ID that is a string, integer, boolean, array, map, or null. This means that when making findByID or insert calls you now need to provide a DittoDocumentID object rather than a string. Similarly, when you access a document's ID it will now return a DittoDocumentID object instead of a string.
  • The start() and stop() functions on the Ditto object have been renamed to startSync() and stopSync() respectively. They now also don't accept any arguments. If you wish to specify which transports you would like the Ditto SDK to make use of (along with any configuration that they might require) you now need to use the setTransportConfig function on the Ditto object, and pass to that a transport config object. The default transports that will be enabled are still the same as they were in previous releases of the SDK though, so if you have no custom requirements then you can simply change your start() call to startSync().
• Lots of performance improvements and bug fixes.

implementation "live.ditto:dittosynckit:1.0.0"

• Fixed a bug where mDNS advertising may continue after Ditto is stopped.
• Fixed a hang that could occur creating an attachment fetcher while requesting many attachments at once.
• Fixed sync failure when there are multiple overlapping subscriptions or live queries with the same query string for the same collection.
• Fixed a potential crash and other sync failures that could occur under certain conditions.

implementation "live.ditto:dittosynckit:1.0.0-alpha9"

• Site IDs, which make up part of a Ditto identity object, are now unsigned, 64-bit integers instead of unsigned 32-bit integers.
• Fix a crash that could occur if an offset with a value greater than the number of matching documents was provided.

implementation "live.ditto:dittosynckit:1.0.0-alpha8"

• Synchronized version bump release

• Performance and stability improvements.
• Fix default data insertion such that merge semantics are consistent and duplicate data isn't created.
• Fixed a bug where documents containing attachments syncing to an instance of the C++ SDK could lead to a crash.
• Upgrade nlohmann json header from 3.7.0 to 3.9.1.
• Added set_custom_log_cb and set_log_file method calls to Log class to allow provision of a custom logging callback function, and a file path that logs should be directed to.

• Added a new intermediate security identity for a shared secret key. This is a simplistic authentication mode which is normally only suitable for private apps where all the users and devices are trusted.
• Fixed an issue that prevented Counter values from syncing correctly
• Renamed DittoAttachmentStatus to DittoAttachmentFetchEvent and subsequently Incomplete status to Progre ss.

• Initial release of the SDK

• This release is not compatible with any previous SDK releases. There are a number of breaking changes both in terms of the SDK API and in terms of the internal systems used by the SDK to perform operations such as synchronization. If you have previously made use of the Ditto SDK and wish to update to this version then note that you will need to delete all existing Ditto data otherwise you will run into errors. If you have existing data that you need to keep then please contact us and we can advise you as to how you can migrate your data.
• The most notable API breaking changes are:
  • Document IDs are no longer restricted to just strings. You can now create a document ID that is a string, integer, boolean, array, map, or null. This means that when making find_by_id or insert calls you now need to provide a DocumentId object rather than a string. Similarly, when you access a document's ID it will now return a DocumentId object instead of a string.
  • The start() and stop() functions on the Ditto object have been renamed to start_sync() and stop_sync() respectively. They now also don't accept any arguments. If you wish to specify which transports you would like the Ditto SDK to make use of (along with any configuration that they might require) you now need to use the set_transport_config function on the Ditto object, and pass to that a transport config object. The default transports that will be enabled are still the same as they were in previous releases of the SDK though, so if you have no custom requirements then you can simply change your start() call to start_sync().
• Lots of performance improvements and bug fixes.

• Fixed a bug where mDNS advertising may continue after Ditto is stopped.
• Fixed a hang that could occur creating an attachment fetcher while requesting many attachments at once.
• Fixed sync failure when there are multiple overlapping subscriptions or live queries with the same query string for the same collection.
• Fixed a potential crash and other sync failures that could occur under certain conditions.

• Site IDs, which make up part of a Ditto identity object, are now unsigned, 64-bit integers instead of unsigned 32-bit integers.
• Fix a crash that could occur if an offset with a value greater than the number of matching documents was provided.

• Synchronized version bump release

Install-Package DittoSharp -Version 1.0.0-alpha7

<PackageReference Include="DittoSharp" Version=1.0.0-alpha7" />

• Performance and stability improvements.
• Fix default data insertion such that merge semantics are consistent and duplicate data isn't created.

Install-Package DittoSharp -Version 1.0.0-alpha6

<PackageReference Include="DittoSharp" Version=1.0.0-alpha6" />

• Added a new intermediate security identity for a shared secret key. This is a simplistic authentication mode which is normally only suitable for private apps where all the users and devices are trusted.
• Fixed an issue that prevented Counter values from syncing correctly
• Renamed DittoAttachmentStatus to DittoAttachmentFetchEvent and subsequently Incomplete status to Progre ss.

Install-Package DittoSharp -Version 1.0.0-alpha5

<PackageReference Include="DittoSharp" Version=1.0.0-alpha5" />

• Fix issue where attachments could stop being fetched incorrectly.
• Introduce a DittoLogger class with various log-related functionality to make logging easier and more feature-rich.

Install-Package DittoSharp -Version 1.0.0-alpha4

<PackageReference Include="DittoSharp" Version=1.0.0-alpha4" />

• Added new observeWithNextSignal API to allow the application to control the delivery of the next observe callback ev ent.
• Fixed several issues related to attachments that could delay sync.
• Simplified log statements

Install-Package DittoSharp -Version 1.0.0-alpha3

<PackageReference Include="DittoSharp" Version=1.0.0-alpha3" />

Fixed several potential issues with attachment fetching that may result in the fetch callback not firing.

Install-Package DittoSharp -Version 1.0.0-alpha2

<PackageReference Include="DittoSharp" Version=1.0.0-alpha2" />

• Note that this is a release with breaking changes and clients using releases in the 1.0 series will not be able to communicate with clients running a version that is anything less than 1.0. This should hopefully not be an issue because this release of the SDK has changed the name to be DittoSyncKit as opposed to DittoSharp and the namespace has gone from DittoSharp to Ditto.SyncKit.
• Lots of performance improvements and some bug fixes.

Install-Package DittoSharp -Version 1.0.0-alpha1

<PackageReference Include="DittoSharp" Version=1.0.0-alpha1" />

• Fixed an issue where extensive writes can cause a session time-out

Install-Package DittoSharp -Version 0.4.0-alpha5

<PackageReference Include="DittoSharp" Version=0.4.0-alpha5" />

• Fixes an issue where deletes might not propagate correctly in a multi-hop mesh

Install-Package DittoSharp -Version 0.4.0-alpha4

<PackageReference Include="DittoSharp" Version=0.4.0-alpha4" />

• Fix disposal/clean-up of DittoAttachmentFetcher objects.
• Add support for Linux 64-bit platforms.

Install-Package DittoSharp -Version 0.4.0-alpha3

<PackageReference Include="DittoSharp" Version=0.4.0-alpha3" />

• Fix a potential crash when working with attachments.

Install-Package DittoSharp -Version 0.4.0-alpha2

<PackageReference Include="DittoSharp" Version=0.4.0-alpha2" />

• Note that this is a release with breaking changes, even just in terms of clients running 0.4.0 not being able to communicate with clients running 0.3.X releases.
• Fixes for memory leaks.
• Performance improvements.

Install-Package DittoSharp -Version 0.4.0-alpha1

<PackageReference Include="DittoSharp" Version=0.4.0-alpha1" />

• Fixed an issue where inserting data as default data (setting the isDefault parameter to true) could lead to data that would not merge as expected.

Install-Package DittoSharp -Version 0.3.5-alpha1

<PackageReference Include="DittoSharp" Version=0.3.5-alpha1" />

• Fixed a bug with query compilation where integer literals in the query would lead to a query compilation failure.

Install-Package DittoSharp -Version 0.3.4-alpha1

<PackageReference Include="DittoSharp" Version=0.3.4-alpha1" />

Compatibility update for 0.3.1 releases.

Install-Package DittoSharp -Version 0.3.1-alpha1

<PackageReference Include="DittoSharp" Version=0.3.1-alpha1" />

Further compatibility updates.

Install-Package DittoSharp -Version 0.1.1-alpha2

<PackageReference Include="DittoSharp" Version=0.1.1-alpha2" />

Compatibility update.

Install-Package DittoSharp -Version 0.1.1-alpha1

<PackageReference Include="DittoSharp" Version=0.1.1-alpha1" />

• Added the licenses of the dependencies used by the SDK to the NuGet package

Install-Package DittoSharp -Version 0.1.0-alpha4

<PackageReference Include="DittoSharp" Version=0.1.0-alpha4" />

• Sorted out the packaging so that installing the SDK doesn't require any extra actions after installation.

Install-Package DittoSharp -Version 0.1.0-alpha3

<PackageReference Include="DittoSharp" Version=0.1.0-alpha3" />

• This release is not compatible with any previous SDK releases. There are a number of breaking changes both in terms of the SDK API and in terms of the internal systems used by the SDK to perform operations such as synchronization. If you have previously made use of the Ditto SDK and wish to update to this version then note that you will need to delete all existing Ditto data otherwise you will run into errors. If you have existing data that you need to keep then please contact us and we can advise you as to how you can migrate your data.
• The most notable API breaking changes are:
  • Document IDs are no longer restricted to just strings. You can now create a document ID that is a string, integer, boolean, array, map, or null. This means that when making FindByID or insert calls you now need to provide a DittoDocumentID object rather than a string. Similarly, when you access a document's ID it will now return a DittoDocumentID object instead of a string.
  • The Start() and Stop() functions on the Ditto object have been renamed to StartSync() and StopSync() respectively. They now also don't accept any arguments. If you wish to specify which transports you would like the Ditto SDK to make use of (along with any configuration that they might require) you now need to use the SetTransportConfig function on the Ditto object, and pass to that a transport config object. The default transports that will be enabled are still the same as they were in previous releases of the SDK though, so if you have no custom requirements then you can simply change your Start() call to StartSync().
• Lots of performance improvements and bug fixes.

Install-Package DittoSharp -Version 1.0.0

<PackageReference Include="DittoSharp" Version=1.0.0" />

• The exact version of the Ditto SDK can now be retrieved using the ditto.SDKVersion property.
• Fixed a bug where mDNS advertising may continue after Ditto is stopped.
• Fixed a hang that could occur creating an attachment fetcher while requesting many attachments at once.
• Fixed sync failure when there are multiple overlapping subscriptions or live queries with the same query string for the same collection.
• Fixed a potential crash and other sync failures that could occur under certain conditions.

Install-Package DittoSharp -Version 1.0.0-alpha9

<PackageReference Include="DittoSharp" Version=1.0.0-alpha9" />

• Site IDs, which make up part of a Ditto identity object, are now unsigned, 64-bit integers instead of unsigned 32-bit integers.
• Fix a crash that could occur if an offset with a value greater than the number of matching documents was provided.

Install-Package DittoSharp -Version 1.0.0-alpha8

<PackageReference Include="DittoSharp" Version=1.0.0-alpha8" />