ANR with Statsig.shutdown()

[nominalista]

According to the docs, it's recommended to call Statsig.shutdown() when closing the app to make sure all events and logs are stored. However, such implementation causes ANR errors when the Activity is getting destroyed:

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        initializeAnalytics()
        // setting up activity here
    }

    override fun onDestroy() {
        super.onDestroy()
        shutdownAnalytics()
    }

    private fun initializeAnalytics() {
        lifecycleScope.async {
            Statsig.initialize(application, STATSIG_SDK_KEY, StatsigUser())
            Log.d(TAG, "Statsig initialized")
        }
    }

    private fun shutdownAnalytics() {
        // Makes sure all logged events are properly flushed or saved locally
        Log.d(TAG, "Shutting down Statsig…")
        Statsig.shutdown()
    }

    // rest of the code…
}

Is this incorrect implementation or defect in 4.44.0?

[kevin-statsig]

Just for clarification: did this code sample not produce an ANR for you before updating to 4.44.0?

I ask because there were some recent updates to some of the logging behavior, but they should have minimal/no impact on the ANR risk.

In its current state, Statsig.shutdown() is a blocking call on the main thread, so it's possible to ANR. This is something we are planning to improve in the future.

My more targeted advice: Since your code sample is Kotlin, consider calling shutdownSuspend(), which doesn't block - though there's less of a guarantee that all logs will be flushed before the process dies.

[nominalista]

I didn't check releases prior 4.44.0, instead I followed the documentation. I decided not to call shutdown at all, but it would be great to have fully working example with basic initialization and shutdown (if shutdown is recommended to call). Modern Android development is tricky and there's very easy to make a mistake, so it would great to see in such example in what lifecycle moments those functions are called.

[kevin-statsig]

I didn't check releases prior 4.44.0

Thanks for confirming.

Thanks also for the documentation feedback - I agree that it could use a bit more detail on lifecycle integration.