Skip to content

Releases: optimizely/android-sdk

Release 5.0.0

25 Nov 14:52
@muzahidul-opti muzahidul-opti
5.0.0
900ffc7
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 (#497)
  • 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

13 Nov 13:53
@muzahidul-opti muzahidul-opti
4.1.0
b5e8a64
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 13th, 2024

New Features

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

Release 4.0.4

18 Sep 17:00
@muzahidul-opti muzahidul-opti
4.0.4
7d7357c
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.4

4.0.4

September 18th, 2024

Bug Fixes

  • R8 configuration breaks Gson use at runtime (#493).
Assets 2
Loading

Release 4.0.3

23 Aug 17:50
@muzahidul-opti muzahidul-opti
4.0.3
70d50b9
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.3

4.0.3

August 23th, 2024

  • Rollback to 4.0.0 (#488).
Assets 2
Loading

Release 4.0.2

20 Aug 15:57
@muzahidul-opti muzahidul-opti
4.0.2
049ec0a
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.2

4.0.2

August 20th, 2024

  • Forward exceptions for unexpected response from ODP (#488).
Assets 2
Loading

Release 4.0.1

31 Jul 23:36
@jaeopt jaeopt
4.0.1
7d59eac
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.1

4.0.1

July 31st, 2024

  • Forward exceptions for ODP fetch segments (#483).
Assets 2
Loading

Release 4.0.0

17 Jan 19:57
@jaeopt jaeopt
4.0.0
0b6f346
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

January 17th, 2024

New Features

The 4.0.0 release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#431,#440,#444,#445,#448,#470).

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.
  • minimum Android API level requirements upgraded to 21 or higher.

Bug Fixes

  • support arbitrary client names to be included in logx and odp events. (#459).
  • Added catch block to capture resource not found exception. (#460).
  • Added a proguard rule to suppress warning for java.beans.Transient. Upgraded Java to 11. (#471).
  • Added a proguard rule to keep ODPEvent and added sample codes for ODP. (#456).

Functionality Enhancements

  • Update Github Issue Templates (#461)
Assets 2
Loading

Release 4.0.0-beta3

21 Sep 08:05
@muzahidul-opti muzahidul-opti
4.0.0-beta3
0da9e47
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-beta3 Pre-release
Pre-release

4.0.0-beta3

September 20th, 2023

Bug Fixes

  • support arbitrary client names to be included in logx and odp events. (#459).
  • Added catch block to capture resource not found exception. (#460).

Functionality Enhancements

  • Update Github Issue Templates (#461)
Assets 2
Loading

Release 4.0.0-beta2

08 May 20:42
@mnoman09 mnoman09
4.0.0-beta2
73959f9
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-beta2 Pre-release
Pre-release

4.0.0-beta2

May 8th, 2023

Bug Fixes

  • Added a proguard rule to keep ODPEvent and added sample codes for ODP. (#456).
Assets 2
Loading

Release 4.0.0-beta

05 May 17:58
@jaeopt jaeopt
4.0.0-beta
7b74992
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 4th, 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)](https://docs.developers.optimizely.com/optimizely-data-platform/docs (#431,#440,#444,#445,#448).

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.
  • minimum Android API level requirements upgraded to 21 or higher.
Assets 2
Loading