Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 36 million developers.Sign up
[4.0.0] - 2019-04-18
This is the first non-beta release of the Swift SDK. It follows the beta.3 release from 2019-03-07. Unlike previous Swift SDK releases, this release does not have a
3.0.0 companion tag.
- Changes Feature Flag caching so that cached feature flags are associated with a user key and mobile key.
- Clears new warnings that appear with Xcode 10.2
- Implements URL caching for REPORT requests.
- Installs the ability to read cached data in all cached data schemas from
3.0.1and store the feature flags in the
4.0.0cached data schema.
- Retains prior cached data for 90 days following upgrade to
4.0.0. Does not keep older cached data up-to-date. Downgrading to a prior version within 90 days allows the downgraded app to read the last cached data from the downgraded version.
- Prevents a log message that incorrectly reported a network error on watchOS
[3.0.0] - 2019-04-17
- Renamed the non-iOS Darkly frameworks to include the platform name. e.g. Darkly_watchOS. Because non-CocoaPods apps will need to update imports for the new modules, advanced to the next major version.
- Removed DarklyEventSource as a CocoaPods dependency in the podfile. DarklyEventSource remains a dependency in the podspec.
[2.14.4] - 2019-02-26
- Changed the following to repair macOS builds:
- Removed extraneous framework reference from Darkly_macOS target
Autocreate schemesin Darkly.xcworkspace
[2.14.3] - 2019-02-25
- Added support for integrating without a package manager
- Updated to
4.0.1, which adds platform specific targets to support integration without a package manager.
[2.14.2] - 2019-01-24
- Added nullability specifiers to public SDK classes.
- Updated to
4.0.0, which eliminates a 1-second delay in SDK initialization.
[2.14.1] - 2018-12-21
- Added copy methods to several objects involved in creating a summary event.
- Added additional synchronization to creating a summary event in order to potentially prevent some crash scenarios.