Releases: launchdarkly/ios-client-sdk
Releases · launchdarkly/ios-client-sdk
[4.2.1] - 2019-11-15
[4.2.0] - 2019-10-25
Added
- The
identify
function allows a completion to be called after a user is updated. - The Connection Status API allows greater introspection into the current LaunchDarkly connection and the health of local flags.
• This feature adds a new class calledConnectionInformation
that contains properties that keep track of the current connection mode e.g. streaming or polling, when and how a connection failed, and the last time flags were updated. This class can be accessed fromLDClient.shared.getConnectionInformation
.
• Additionally, a new observer function calledobserveCurrentConnectionMode
allows your application to listen to changes in the SDK's connection to LaunchDarkly.
Changed
- The
user
property is now deprecated in favor of theidentify
function.
[4.1.2] - 2019-07-11
Fixed
- WatchKit is now conditionally imported in WatchOS only to fix an error in Xcode 11.
- Comparing two nil objects of type [String: Any]? no longer causes a crash.
[4.1.1] - 2019-07-09
Change
- Updated to
ios-eventsource
version4.0.2
. This fixes a potential hang on LDClient start.
[3.0.4] - 2019-07-09
Changed
- Updated to
ios-eventsource
version4.0.2
. This fixes a potential hang on LDClient start.
[4.1.0] - 2019-06-19
Change
- Installs new
deviceModel
intoEnvironmentReporter
and renames olddeviceModel
todeviceType
. - Updated MacOS model detection to use
CwSysCtl
.
Fixed
- Fixed a concurrency bug that caused crashes in FlagStore.swift. This bug could surface during rapid updates to local flags.
3.0.3
[3.0.3] - 2019-05-30
Changed
- Added
nonnull
tofeatureKey
parameters on exposed variation methods.
Fixed
- Added length check to
flagConfigValueForKey
to prevent dictionary access when key is nil.
3.0.2
[3.0.2] - 2019-05-15
Changed
- Moved the timer that limits how often a client app can set the SDK online onto the main run loop.
4.0.0
[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.
Changed
- 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
Added
- Implements URL caching for REPORT requests.
- Installs the ability to read cached data in all cached data schemas from
2.3.3
through3.0.1
and store the feature flags in the4.0.0
cached 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.
Fixed
- Prevents a log message that incorrectly reported a network error on watchOS
3.0.1
[3.0.1] - 2019-04-30
Changed
- Deployed Carthage built DarklyEventSource frameworks as part of the Darkly project.