CloudBees Feature Management - Android changelog

new RoxVariant("defaultStr", new String[] {"str1", "str2"}) ⇒ new RoxString("defaultStr", new String[] {"str1", "str2"}).

new RoxEnumVariant<>(MyEnumType.Value) ⇒ new RoxEnum<>(MyEnumType.Value).

Some trivial parameters (mostly type) validations were added to dynamicApi and flags constructions. For example: new RoxString(null) will raise an IllegalArgumentException as default cannot be null (default value of RoxString should be a string). Rox.dynamicApi.value(null, "defaultStr", ["str2", "str3"]) will raise an IllegalArgumentException because of null flag name (name should always be a string).

register(container) will register the container under an empty string namespace (multiple register calls with the same namespaces are still not allowed!).

It is recommended to wrap all handlers used in Rox platform (all CustomPropertyGenerator.generateProperty, ImpressionHandler.onImpression, ConfigurationFetchedHandler.onConfigurationFetched, DynamicPropertyRule.invoke) with try-catch in order to be in the right context. In case there will be an uncaught error, it will reach the Rox.setUserspaceUnhandledErrorHandler handler. You can use this handler for debugging, or for further error handling. A Throwable thrown within this handler will be written to log. If no setUserspaceUnhandledErrorHandler was set, errors will be written to the log.

Starting with SDK 5, flags will always send impressions after setup (not only when targeting is enabled on the dashboard).

As experiments were removed, impressions handler signature was changed from (reportingValue, experiment, context) to (ImpressionEvent event). Besides name, value, and context properties, event also provides targeting (boolean) property, indicating the flag was evaluated by using the dashboard configurations.

In addition to RoxFlag and RoxString, we also added RoxInt and RoxDouble

DynamicApi was also updated with matching getInt and getDouble methods.

In order to clean all background tasks.

multiple Rox.setup calls will be ignored if Rox wasn’t shutdown in between.

In order to maintain the old behavior please add to your setup options RoxOptions.Builder.withFreeze(Freeze.UntilLaunch). If there’s no options object currently, add it to your setup call: Rox.setup(app, new RoxOptions.Builder().withFreeze(Freeze.UntilLaunch).build())

new RoxConfigurationString ⇒ new RoxString

new RoxConfigurationInt ⇒ new RoxInt

new RoxConfigurationDouble ⇒ new RoxDouble

new RoxConfigurationBool ⇒ new RoxFlag

Custom properties can now use context too via the overloaded Rox.setCustomXXXProperty methods accepting CustomPropertyGeneratorWithContext<> argument.

.none - The flag is constantly evaluated every time it is called

.untilForeground (default) - Once the flag is evaluated its value is persistent until the next foreground/ unfreeze event

.untilLaunch - Once the flag is evaluated its value is persistent till the app is terminated You can control the value of a specific flag via its constructor or globally by using RoxOptions.withFreeze method