Frequently Asked Questions

Date of slack thread: 6/3/24

Anonymous: Hey! Do I need to handle running statsig initialise on an IO thread, or is this handled in the implementation

Statbot: When initializing Statsig in a client application, especially on platforms like Android, it’s important to consider thread management because network operations can block the main thread, leading to a poor user experience. The documentation provides examples of both synchronous and asynchronous initialization. For asynchronous initialization, a callback is provided, which allows you to wait for the most current data to be fetched without blocking the main thread. Here’s an example of asynchronous initialization from the documentation:

client.InitializeAsync(
    "client-{YOUR_CLIENT_SDK_KEY}",
    [](StatsigResultCode result) {
        // completion callback
    },
    user
);

In this case, the InitializeAsync method is designed to be non-blocking and should handle running the initialization on a separate thread internally, so you wouldn’t need to explicitly run initialize on an IO thread yourself. This is a common pattern in SDKs to ensure that the main thread remains responsive while the SDK performs network operations in the background source. For other platforms or languages, you should refer to the specific documentation for that SDK to understand how it handles threading for initialization. If you’re using a server-side SDK or a different client-side SDK, the approach may vary. If you have a specific SDK in mind, please let me know, and I can provide more detailed guidance based on the documentation.

Statbot: Click below to mark as resolved.

Statbot: This thread has been marked as resolved. Press below to re-open.

Statbot: Thread has been re-opened, click below to mark as resolved again.

Anonymous: Under what conditions will InitializationDetails be null

Anonymous: @Statbot Under what conditions will InitializationDetails be null