Merge branch 'master' into muzahid/update-license-year

Author: muzahidul-opti

.github/workflows/integration_tests.yml

@@ -20,14 +20,18 @@ jobs:
         path: 'home/runner/travisci-tools'
         ref: 'master'
     - name: set SDK Branch if PR
+      env: 
+        HEAD_REF: ${{ github.head_ref }}
       if: ${{ github.event_name == 'pull_request' }}
       run: |
-        echo "SDK_BRANCH=${{ github.head_ref }}" >> $GITHUB_ENV
+        echo "SDK_BRANCH=$HEAD_REF" >> $GITHUB_ENV
     - name: set SDK Branch if not pull request
+      env:
+        REF_NAME: ${{ github.ref_name }}
       if: ${{ github.event_name != 'pull_request' }}
       run: |
-        echo "SDK_BRANCH=${{ github.ref_name }}" >> $GITHUB_ENV
-        echo "TRAVIS_BRANCH=${{ github.ref_name }}" >> $GITHUB_ENV
+        echo "SDK_BRANCH=$REF_NAME" >> $GITHUB_ENV
+        echo "TRAVIS_BRANCH=$REF_NAME" >> $GITHUB_ENV
     - name: Trigger build
       env:
         SDK: swift

.github/workflows/swift.yml

@@ -17,7 +17,7 @@ on:
         description: release
 
 env:
-  VERSION: 3.10.4
+  VERSION: 4.1.0
 
 jobs:
 

.github/workflows/unit_tests.yml

@@ -54,13 +54,17 @@ jobs:
           # macos version and supported simulator_xcode_versions are all related to this xcode_version, so be careful when you upgrade this.
           xcode-version: 14.1
       - name: set SDK Branch if PR
+        env:
+          BASE_REF: ${{ github.base_ref }}
         if: ${{ github.event_name == 'pull_request' }}
         run: |
-          echo "BRANCH=${{ github.base_ref }}" >> $GITHUB_ENV
+          echo "BRANCH=$BASE_REF" >> $GITHUB_ENV
       - name: set SDK Branch if not pull request
+        env:
+          REF_NAME: ${{ github.ref_name }}
         if: ${{ github.event_name != 'pull_request' }}
         run: |
-          echo "BRANCH=${{ github.ref_name }}" >> $GITHUB_ENV
+          echo "BRANCH=$REF_NAME" >> $GITHUB_ENV
       - id: unit_tests
         env:
           SCHEME: ${{ matrix.scheme }}
@@ -89,7 +93,7 @@ jobs:
           Scripts/prepare_simulator.sh
           Scripts/run_unit_tests.sh
       - name: Check on failures (Archive Test Results)
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         if: steps.unit_tests.outcome != 'success'
         with:
           name: build-logs-${{ matrix.device }}-${{ matrix.os }}

CHANGELOG.md

@@ -1,5 +1,68 @@
 # Optimizely Swift SDK Changelog
 
+## 4.1.0
+November 8, 2024
+
+### New Features
+* Batch UPS lookup and save calls in decideAll and decideForKeys methods ([#559](https://github.com/optimizely/swift-sdk/pull/559/)).
+
+## 4.0.0
+Jan 18, 2024
+
+### New Features  
+
+The 4.0.0 release introduces a new primary feature, [Advanced Audience Targeting]( https://docs.developers.optimizely.com/feature-experimentation/docs/optimizely-data-platform-advanced-audience-targeting) enabled through integration with [Optimizely Data Platform (ODP)](https://docs.developers.optimizely.com/optimizely-data-platform/docs) ([#455](https://github.com/optimizely/swift-sdk/pull/455), [#470](https://github.com/optimizely/swift-sdk/pull/470), [#471](https://github.com/optimizely/swift-sdk/pull/471), [#477](https://github.com/optimizely/swift-sdk/pull/477),[#512](https://github.com/optimizely/swift-sdk/pull/512)). 
+
+You can use ODP, a high-performance [Customer Data Platform (CDP)]( https://www.optimizely.com/optimization-glossary/customer-data-platform/), 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:  
+
+* [Advanced Audience Targeting](https://docs.developers.optimizely.com/feature-experimentation/docs/optimizely-data-platform-advanced-audience-targeting)  
+
+* [Client SDK Support](https://docs.developers.optimizely.com/feature-experimentation/v1.0/docs/advanced-audience-targeting-for-client-side-sdks) 
+
+* [Initialize Swift SDK](https://docs.developers.optimizely.com/feature-experimentation/docs/initialize-sdk-swift) 
+
+* [OptimizelyUserContext Swift SDK](https://docs.developers.optimizely.com/feature-experimentation/docs/optimizelyusercontext-swift) 
+
+* [Advanced Audience Targeting segment qualification methods](https://docs.developers.optimizely.com/feature-experimentation/docs/advanced-audience-targeting-segment-qualification-methods-swift) 
+
+* [Send Optimizely Data Platform data using Advanced Audience Targeting](https://docs.developers.optimizely.com/feature-experimentation/docs/send-odp-data-using-advanced-audience-targeting-swift) 
+
+### 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](https://github.com/optimizely/swift-sdk/pull/514))
+* Remove redundant post request body in upload task. ([#521](https://github.com/optimizely/swift-sdk/pull/521/)).
+* Privacy manifest file value for required reason API fixed. ([#541](https://github.com/optimizely/swift-sdk/pull/541))
+* Add coccoapods support for privacy manifest. ([#542](https://github.com/optimizely/swift-sdk/pull/542))
+* Add SPM support added to process privacy manifest. ([#544](https://github.com/optimizely/swift-sdk/pull/544))
+
+### Functionality Enhancement
+* Adds support to override sdkName and sdkVersion for events. ([#512](https://github.com/optimizely/swift-sdk/pull/512))
+* Swift async-await support. ([#513](https://github.com/optimizely/swift-sdk/pull/513))
+* Update Github Issue Templates. ([#516](https://github.com/optimizely/swift-sdk/pull/516))
+* Handle duplicate keys in experiment ([#523](https://github.com/optimizely/swift-sdk/pull/523/)).
+* Add privacy manifest file ([#522](https://github.com/optimizely/swift-sdk/pull/522/)).
+
 ## 3.10.4
 December 8, 2023
 

OptimizelySwiftSDK.podspec

@@ -1,7 +1,7 @@
 Pod::Spec.new do |s|
   s.name                    = "OptimizelySwiftSDK"
   s.module_name	            = "Optimizely"
-  s.version                 = "4.0.0-beta"
+  s.version                 = "4.1.0"
   s.summary                 = "Optimizely experiment framework for iOS/tvOS/watchOS"
   s.homepage                = "https://docs.developers.optimizely.com/experimentation/v4.0.0-full-stack/docs"
   s.license                 = { :type => "Apache License, Version 2.0", :file => "LICENSE" }