Java SDK 4.24.3

Bug fixes

• Fixed a false-positive Unexpected TargetingOperator: null error log when the SDK loads a configuration containing a BROWSER or SDK_LANGUAGE targeting condition without a version. Such conditions are valid and were evaluated correctly; only the log message was spurious.

Java SDK 4.24.2

Bug fixes

• Fixed excessive SSE reconnection attempts and logging: the SDK now waits the configured delay before reconnecting after any server-side close or connection failure, and no longer attempts to reconnect after unsubscribe.
• Replaced httpasyncclient 4.1.5 with httpcore 4.4.16.
• Updated:
  • httpclient5 5.3.1 → 5.6.4
  • commons-lang3 3.18.0 → 3.20.0
  • org.jetbrains:annotations 26.0.1 → 26.1.0
  • parsson (Jakarta build) 1.1.6 → 1.1.9

Java SDK 4.24.1

Bug fixes

• Reduced the load on the Data API during its outages. After a failed tracking request, the SDK sends only one visitor's data per tracking request until a request succeeds, instead of retrying with a full-size (up to 2.5 MB) request on every tracking interval. Once the Data API is reachable again, the accumulated visitor data is sent in full-size requests as usual.

Java SDK 4.24.0

Features

• Added the new waitInit(timeoutMillis) overload, which limits how long the returned future may stay pending. The future settles with the result of the configuration fetch (successfully once the SDK is ready, or exceptionally with KameleoonException.Initialization as soon as the fetch has failed); if no fetch result is available within the timeout, it completes exceptionally with KameleoonException.Initialization caused by a TimeoutException.
• Added the new KameleoonException.Initialization exception, which waitInit now fails with when the SDK could not be initialized. The former KameleoonException.SDKNotReady is deprecated; it remains catchable because Initialization extends it, and will be removed in the next major release.

Bug fixes

• Targeting conditions of unknown (unsupported) types are now evaluated to false instead of true, so visitors are no longer targeted by segments containing web-specific conditions the SDK does not support.

Java SDK 4.23.0

Features

• Added the new [isReady][isReady] method, which returns true once the SDK has successfully loaded its configuration and is ready for use, and false otherwise (for example, while initialization is still in progress or has failed). Unlike waitInit, it returns immediately without blocking or throwing.
  [isReady]: https://docs.kameleoon.com/developer-docs/sdks/web-sdks/java-sdk#isready

Java SDK 4.22.0

Features

• Added support for SDK event handlers through the new [setEventHandler][setEventHandler] API:
  • DATAFILE_UPDATE notifies when the SDK data file (configuration) is updated with polling or streaming modes.
  • HTTP_REQUEST notifies when SDK HTTP requests complete successfully or fail.
  • HTTP request events include the request type, HTTP status or failure details, and request duration.
  • Passing null to setEventHandler clears the handler for the selected event type.
    [setEventHandler]: https://docs.kameleoon.com/developer-docs/sdks/web-sdks/java-sdk#seteventhandler

Java SDK 4.21.0

Features

• Added support for *during the current visit- and *during any of the last visits- settings across the following targeting conditions:
  • Converted Goal
  • Feature Flag
  • Web Experiment
  • Personalization
  • Exclusive Campaign

Java SDK 4.19.0

Features

• Introduced support for the Kameleoon ApplicationVersion data type, allowing the visitor’s application version to be set and used in targeting evaluation.
• Updated the allowed range for the trackingInterval. The new range is from *1000 ms- (default) to 5000 ms, allowing a reduction in the number of tracking requests.
• Introduced a new track parameter for addData. When set to false, the data is stored locally and used only for targeting evaluation; it is not sent to the Data API, helping to prevent duplicate data from being recorded. The default value is true. This behavior is consistent with the track parameter used in evaluation methods such as getVariation.

Java SDK 4.18.1

Bug fixes

• Fixed an issue where *legal consent- was not taken into account during holdout evaluation.

Java SDK 4.18.0

Features

• Updated evaluation and tracking logic to comply with GDPR requirements when consent is not given:
  • If behavior is partially blocked, the default variation will be returned.
  • If behavior is completely blocked, an exception will be thrown.