Releases: adobe/aepsdk-target-ios
v5.0.0
Release Notes
Major version update for Target for Adobe Experience Platform Mobile SDKs on iOS compatible with Mobile Core 5.0.0. The current release includes the following changes:
- Updated the minimum supported version to iOS 12.0.
- Include XCFrameworks built with Xcode 15.0.1 with the GitHub release.
- Fixed a bug when using Target Preview on device that caused the floating button to remain visible when a preview selection was active.
What’s Changed
- Staging to main for 5.0.0 release (#168) @sbenedicadb
- -fix circle config (#167) @sbenedicadb
- Dev v5.0.0 to staging (#166) @sbenedicadb
- Dev v5.0.0 to staging (#165) @sbenedicadb
- point to staging branches and merge main in (#164) @sbenedicadb
- -remove codecov from dev-v5.0.0 circle script (#163) @sbenedicadb
- Fix for MOB-20343 (#159) @spoorthipujariadobe
v4.0.4
- Added max versions to Platform dependencies in podspec
v4.0.3
Release Notes
- Fixed an issue where Target response tokens were not returned in
TargetRequest
'scontentWithDataCallback
callback when usingretrieveLocationContent
API.
v4.0.2
What’s Changed
- staging to main for 4.0.2 release (#154) @sbenedicadb
- Dev v4.0.2 to staging (#153) @sbenedicadb
- -update version in podspec (#152) @sbenedicadb
- -adding update versions gh action workflow (#151) @sbenedicadb
- X-EXC-SDK support for Target requests (#150) @swarna04
- MOB-19642 (#149) @sbenedicadb
- Added support for X-EXC-SDK & X-EXC-SDK-Version headers (#148) @swarna04
v4.0.1
v4.0.0
v3.3.1
v3.3.0
What’s Changed
- Added new raw Target APIs for mbox content and notifications (#125) @swarna04
- Target release prep + misc fixes (#123) @swarna04
- Added new raw Target APIs for non-unique batch mboxes support (#122) @swarna04
- Support remote updates to Target property token (#121) @swarna04
- dev -> main (v3.2.0) (#118) @swarna04
v3.2.0
Release Notes
Summary
Added getter and setter APIs for Target tnt ID and Target session ID to enable cross-channel sessions. (#118) @swarna04
-
The setSessionId API should be invoked prior to any Target request to prevent the Mobile SDK from generating a session ID locally. The session ID will follow the session expiry as governed by the target.sessionTimeout configuration setting. You can use this API in conjunction with setTntId API to set both of the value in the SDK.
-
The setTntId API, when invoked, also sets the Target edge host value in the SDK by deriving it from the profile location hint supplied in the tnt ID.
-
The getSessionId and getTntId APIs can be used to retrieve the current Target session ID and tnt ID values respectively.