v1.9.1 - add error handling for UAParser

up version to 1.9.1

v1.9.0 - added support for server SDK to bootstrap initialize response for client SDKs

[Internal usage only]

This version of the SDK added support for the server SDK to be able to compose the response for client SDK's initialize requests.

v1.8.0 - added support for getLayer; ID List rework

• Introduces getLayer API to Statsig, adding the ability to get values via a Layer configuration set on the Statsig Console. See docs.statsig.com/layers

• reworked ID list so that it's done in a more efficient way.

v1.7.0 - thread safety improvements

• Added improvements to make the EventLogger and SpecStore thread safe.
• Fixed a bug where the SDK was blocking the background threads when waiting for the next scheduled task.

Thanks to @kroymann for his contribution on these improvements!

v1.6.1 - bug fixes

Fixed a couple bugs:

1. ID list sync could result in a crash if the network request failed. Added logic to handle that
2. Fixed the issue that EventLog was missing timestamp, in which case we were using the time when the log arrives at Statsig server instead of when it was actually created.

v1.6.0 - added option to designate local storage location

Add a new option in StatsigOptions, PersistentStorageFolder, that you can use to choose a folder for the SDK to use to store values to be used across sessions and when the user is offline.

v1.5.0 - added support for customID, ID Lists, and new conditions

• The SDK now supports providing and evaluating using customIDs instead of userID
• now supports evaluating feature gates that rely on ID Lists
• now supports evaluating conditions with operators "is null" and "is not null"

Improvements to experiment exposure logging

1. We have been calculating/logging secondary exposures (exposures on dependent feature gates) in Statsig backend. With this release we are moving the logic to SDK evaluator so that it's more accurate and efficient.
2. Changed ruleID from "default" to "disabled" when evaluating a disabled feature so we can differentiate when gates are returning the default value as the result of evaluation or because the gate is disabled.

Align evaluation behavior for string based operators

We are aligning the behavior for all string based operators in this release so that we try to convert accidentally provided incorrect types to strings and evaluate instead of returning false by default.

Adding support for a new operator

Added support for "string contains none" operator.

Moved exposure logging for "fetch from server" fallback case from SDK to statsig server