v3.2.2

Release notes

• Added timeout (in seconds) parameter to updatePropositions and getPropositions APIs to enable timeout configuration in both the apis ensuring that the operation either completes within the given time frame or returns an error indicating a timeout.
• Updated getPropositions API to return cached propositions immediately if there are no pending updatePropositions calls for the requested list of decision scopes.
• Added support for debug events and enabled getPropositions and onPropositionsUpdate to receive Simulated events from Assurance.

What’s Changed

• Staging to Main (#120) @siddique-adobe
• Dev v3.2.2 to Staging (#118) @siddique-adobe
• Updating version to 3.2.2 (#116) @github-actions
• [MOB-22521] Updating timeout scale to seconds from milliseconds in the updateProposition configurable timeout API (#114) @siddique-adobe
• add separate cache for preview propositions (#113) @ishita-gambhir-adobe

v3.1.0

Release notes

• Added a new updatePropositions API to support completion callback with retrieved propositions and errors (if any).

What’s Changed

• Staging to Main (#100) @siddique-adobe
• Dev v3.1.0 to Staging (#99) @siddique-adobe
• Version updated to 3.1.0 (#98) @siddique-adobe
• Dev v3.1.0 to Staging (#97) @siddique-adobe
• Provide errors and propositions in updateProposition callback (#96) @ishita-gambhir-adobe
• update updateProposition API to provide callback (#94) @ishita-gambhir-adobe

v3.0.2

Release Notes

• Fixed thread safety for map updates that happen when updatePropositions API was called repeatedly.
• Fixed issue where Offer could not be created for default content item when getPropostions API was called.

What’s Changed

• Staging -> Main (#90) @siddique-adobe
• Dev v3.0.2 -> Staging (#89) @siddique-adobe
• [MOB-21446] Fix for missing data field in edge response and adding unit test for the same (#88) @siddique-adobe
• [MOB-21074] Fix threading issues during map updates in updateProposition (#87) @siddique-adobe

v3.0.1

Release Notes

• Fixed a bug where Optimize SDK was considering Target mbox decision scope strings as invalid and not including them in personalization requests.

What’s Changed

• Staging v3.0.1 -> main (#86) @spoorthipujariadobe
• Dev v3.0.1 -> Staging (#85) @spoorthipujariadobe
• Fix DecisionScope.isValid failing for mbox string (#84) @spoorthipujariadobe

v3.0.0

Release Notes

Major version update for Adobe Journey Optimizer - Decisioning Extension for Adobe Experience Platform Mobile SDKs on Android compatible with Mobile Core 3.0.0. The current release includes the following changes:

• Updated the minimum supported Android API level to 21.
• Removed deprecated registerExtension API. Use the MobileCore.registerExtensions() API for registering extensions and initializing the SDK instead.
• Renamed class Proposition to OptimizeProposition.

What’s Changed

• To Main : v3.0.0 release (#81) @PravinPK
• Merge dev-v3.0.0 to staging (#80) @spoorthipujariadobe
• Merge staging into Dev v3.0.0 (#79) @spoorthipujariadobe
• final changes for 3.0.0 release (#78) @spoorthipujariadobe
• change namespace to avoid conflicts (#77) @spoorthipujariadobe
• Update module version for beta 1 release (#76) @PravinPK
• License Header + Run Spotless (#75) @PravinPK
• Android 3.x changes, Gradle, CI, Github actions (#74) @PravinPK

v2.0.2

Release Notes

• Added support for streamlining processing order for update and get propositions events.

v2.0.1

What's Changed

• Verify configuration shared state is set before processing proposition requests by @swarna04 in #67

v2.0.0

What's Changed

• [v2.0.0] staging -> main by @swarna04 in #52

Full Changelog: v1.0.1...v2.0.0

v1.0.0

Release Notes

Summary

• AEPOptimize mobile SDK v1.0.0 provides APIs to enable real-time personalization workflows in mobile apps using Adobe Target or Adobe Journey Optimizer Offer Decisioning.

For more details, refer to the extension documentation here.

What's Changed

• Optimize Android SDK Release v1.0.0 by @swarna04 in #27

v1.0.1

Release Notes

Summary

• Fixed an issue where Base64 encoding the JSON string, created using the activityId and placementId provided in the DecisionScope constructor, introduced a newline character in the encoded scope string.

What's Changed

• MOB-17465 [Android] Fixed decision scope encoding issue by @swarna04 in #31