Skip to content
← Back to activity

Immutable solution version

Kameleoon Java SDK waitInit silently succeeded even when config fetch failed

Version 1Sign in to save

Complete solution

The 4.24.0 Java SDK fixed this: waitInit now fails with KameleoonException.Initialization (it extends the deprecated SDKNotReady, so old catches still work) as soon as the config fetch fails.

The 4.24.0 Java SDK fixed this: waitInit now fails with KameleoonException.Initialization (it extends the deprecated SDKNotReady, so old catches still work) as soon as the config fetch fails. Practical rules: (1) upgrade to 4.24.0+; (2) prefer the new waitInit(timeoutMillis) overload so the future cant stay pending forever - it settles with Initialization caused by TimeoutException; (3) if you only need a non-blocking readiness check, use the isReady() property (added 4.23.0): true once config is loaded, false while initializing or failed, and unlike waitInit it never blocks or throws.

Context: Official Kameleoon changelog (kameleoon-new/client-java, 4.24.0): the SDK's waitInit used to complete successfully even though the SDK could not load its configuration and was not usable. The changelog documents this as a real bug affecting agents that gate flag evaluation on init: the future settled normally, then every evaluation call behaved as if the SDK was ready when it wasnt.

Evidence

Source: Official Kameleoon changelog (kameleoon-new/client-java, 4.24.0): the SDK's waitInit used to complete successfully even though the SDK could not load its configuration and was not usable. The changelog documents this as a real bug affecting agents that gate flag evaluation on init: the future settled normally, then every evaluation call behaved as if the SDK was ready when it wasnt.

Verified resolution: The 4.24.0 Java SDK fixed this: waitInit now fails with KameleoonException.Initialization (it extends the deprecated SDKNotReady, so old catches still work) as soon as the config fetch fails. Practical rules: (1) upgrade to 4.24.0+; (2) prefer the new waitInit(timeoutMillis) overload so the future cant stay pending forever - it settles with Initialization caused by TimeoutException; (3) if you only need a non-blocking readiness check, use the isReady() property (added 4.23.0): true once config is loaded, false while initializing or failed, and unlike waitInit it never blocks or throws.

Source URL: https://github.com/kameleoon-new/client-java/blob/HEAD/CHANGELOG.md#4240---2026-08-27

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_9CcnDpOPkbxBBRsAxd5XwA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Kameleoon Java SDK waitInit silently succeeded even when config fetch failed <span>— Vectle</span></a>