Skip to content

Releases: optimizely/swift-sdk

Release 5.0.0

26 Nov 02:33
@optibot optibot
v5.0.0
b3651f6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Release 5.0.0 Latest
Latest

5.0.0

November 25th, 2024

Breaking Changes

  • VUID configuration is now independent of ODP (#456)
  • When VUID is disabled:
    • vuid is not generated or saved.
    • client-initialized event will not auto fired on SDK init.
    • vuid is not included in the odp events as a default attribute.
    • createUserContext() will be rejected if userId is not provided.
Assets 2
Loading

Release 4.1.0

08 Nov 17:29
@optibot optibot
v4.1.0
5da09ad
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Release 4.1.0

4.1.0

November 8, 2024

New Features

  • Batch UPS lookup and save calls in decideAll and decideForKeys methods (#559).
Assets 2
Loading

Release 4.0.0

19 Jan 01:04
@optibot optibot
v4.0.0
38520c8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Release 4.0.0

4.0.0

Jan 18, 2024

New Features

The 4.0.0 release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#455, #470, #471, #477,#512).

You can use ODP, a high-performance Customer Data Platform (CDP), to easily create complex real-time segments (RTS) using first-party and 50+ third-party data sources out of the box. You can create custom schemas that support the user attributes important for your business, and stitch together user behavior done on different devices to better understand and target your customers for personalized user experiences. ODP can be used as a single source of truth for these segments in any Optimizely or 3rd party tool.

With ODP accounts integrated into Optimizely projects, you can build audiences using segments pre-defined in ODP. The SDK will fetch the segments for given users and make decisions using the segments. For access to ODP audience targeting in your Feature Experimentation account, please contact your Customer Success Manager.

This version includes the following changes:

  • New API added to OptimizelyUserContext:

    • fetchQualifiedSegments(): this API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. The fetched data will be stored in the local cache to avoid repeated network delays.

    • When an OptimizelyUserContext is created, the SDK will automatically send an identify request to the ODP server to facilitate observing user activities.

  • New APIs added to OptimizelyClient:

    • sendOdpEvent(): customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP.

    • createUserContext() with anonymous user IDs: user-contexts can be created without a userId. The SDK will create and use a persistent VUID specific to a device when userId is not provided.

For details, refer to our documentation pages:

Breaking Changes

  • ODPManager in the SDK is enabled by default. Unless an ODP account is integrated into the Optimizely projects, most ODPManager functions will be ignored. If needed, ODPManager can be disabled when OptimizelyClient is instantiated.

Bug Fixes

  • Adds a check to only save valid datafile in cache. (#514)
  • Remove redundant post request body in upload task. (#521).
  • Privacy manifest file value for required reason API fixed. (#541)
  • Add coccoapods support for privacy manifest. (#542)
  • Add SPM support added to process privacy manifest. (#544)

Functionality Enhancement

  • Adds support to override sdkName and sdkVersion for events. (#512)
  • Swift async-await support. (#513)
  • Update Github Issue Templates. (#516)
  • Handle duplicate keys in experiment (#523).
  • Add privacy manifest file (#522).
Assets 2
Loading

Release 3.10.5

19 Jan 17:13
@optibot optibot
v3.10.5
c40a6e6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
Release 3.10.5

3.10.5

Jan 19, 2024

Bug Fixes

  • Value for required reason API fixed at privacy manifest file. (#541)
  • Add coccoapods support to bundle privacy manifest file. (#542)
  • Add SPM support to bundle privacy manifest file. (#544)
Assets 2
Loading

Release 3.10.4

11 Dec 15:33
@optibot optibot
v3.10.4
f774652
Compare
Choose a tag to compare
Release 3.10.4

3.10.4

December 8, 2023

Enhancement

  • Add privacy manifest file (#522).
Assets 2
Loading

Release 3.10.3

08 Dec 12:51
@optibot optibot
v3.10.3
cdd7ecf
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release 3.10.3

3.10.3

December 7, 2023

Bug Fixes

  • Remove redundant post request body in upload task. (#521).

Enhancement

  • Handle duplicate keys in experiment (#523).
Assets 2
Loading

Release 4.0.0-beta

02 May 19:25
@optibot optibot
v4.0.0-beta
64bd9a4
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release 4.0.0-beta Pre-release
Pre-release

4.0.0-beta

May 1, 2023

New Features

The 4.0.0-beta release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#455, #470, #471, #477).

You can use ODP, a high-performance Customer Data Platform (CDP), to easily create complex real-time segments (RTS) using first-party and 50+ third-party data sources out of the box. You can create custom schemas that support the user attributes important for your business, and stitch together user behavior done on different devices to better understand and target your customers for personalized user experiences. ODP can be used as a single source of truth for these segments in any Optimizely or 3rd party tool.

With ODP accounts integrated into Optimizely projects, you can build audiences using segments pre-defined in ODP. The SDK will fetch the segments for given users and make decisions using the segments. For access to ODP audience targeting in your Feature Experimentation account, please contact your Customer Success Manager.

This version includes the following changes:

  • New API added to OptimizelyUserContext:

    • fetchQualifiedSegments(): this API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. The fetched data will be stored in the local cache to avoid repeated network delays.

    • When an OptimizelyUserContext is created, the SDK will automatically send an identify request to the ODP server to facilitate observing user activities.

  • New APIs added to OptimizelyClient:

    • sendOdpEvent(): customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP.

    • createUserContext() with anonymous user IDs: user-contexts can be created without a userId. The SDK will create and use a persistent VUID specific to a device when userId is not provided.

For details, refer to our documentation pages:

Breaking Changes

  • ODPManager in the SDK is enabled by default. Unless an ODP account is integrated into the Optimizely projects, most ODPManager functions will be ignored. If needed, ODPManager can be disabled when OptimizelyClient is instantiated.
Assets 2
Loading

Release 3.10.2

16 Mar 15:37
@optibot optibot
v3.10.2
26c5b02
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release 3.10.2

3.10.2

March 14, 2023

  • We updated our README.md and other non-functional code to reflect that this SDK supports both Optimizely Feature Experimentation and Optimizely Full Stack. (#479).
Assets 2
Loading

Release 3.10.1

08 Apr 20:46
@optibot optibot
v3.10.1
193cc00
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release 3.10.1

3.10.1

April 8, 2022

Bug Fixes

  • Remove sources of race conditions in ProjectConfig (#449).
  • Clean up URLSession after tasks are completed (#446).
Assets 2
Loading

Release 3.10.0

06 Jan 22:50
@optibot optibot
v3.10.0
9c135eb
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
Release 3.10.0

3.10.0

January 6, 2022

New Features

  • Add a set of new APIs for overriding and managing user-level flag, experiment and delivery rule decisions. These methods can be used for QA and automated testing purposes. They are an extension of the OptimizelyUserContext interface (#431, #442, #443):

    • setForcedDecision
    • getForcedDecision
    • removeForcedDecision
    • removeAllForcedDecisions

    For details, refer to our documentation pages: OptimizelyUserContext and Forced Decision methods.

  • Add reachability checking for datafile fetch and event dispatching (#439).

Assets 2
Loading