Crash in migration helper

[androidacy-user]

Hello! On a fresh install, the countly sdk throws an exception, like so:

Process: com.app, PID: 26888
java.lang.AssertionError
	at ly.count.android.sdk.MigrationHelper.doWork(MigrationHelper.java:55)
	at ly.count.android.sdk.Countly.init(Countly.java:550)
	at com.app.MainApplication.initCountly(MainApplication.kt:699)
	at com.app.MainApplication.access$initCountly(MainApplication.kt:163)
	at com.app.MainApplication$onCreate$1$initJobs$2.invokeSuspend(MainApplication.kt:598)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:34)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:124)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:820)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)

Occurs across several different test devices.

[turtledreams]

Hi @androidacy-user ,
Which SDK version you are using? Did you modify SDK code by any chance? Also I assume it happens in a testing scenario with assertions are enabled. From the snippet you shared an assertion that should not fail is failing. I am not able to reproduce this. Can you give more information about you scenario?

[androidacy-user]

Hi @androidacy-user ,
Which SDK version you are using? Did you modify SDK code by any chance? Also I assume it happens in a testing scenario with assertions are enabled. From the snippet you shared an assertion that should not fail is failing. I am not able to reproduce this. Can you give more information about you scenario?

Latest at the time of posting from the Countly maven repo, release and debug builds alike, and it only happens on the first run. The assert it crashes on is the migration logic. It's worked around in our code by retrying init again if the first fails.

[arifBurakDemiray]

Hello @androidacy-user
To inspect the issue in a detailed manner could you please share:

• your IDE and its version
• which android API are you trying with
• do you use some special flag with gradle? enableAssertions = true, -ea (or -enableassertions), or any other assert enable mechanism
• And other platform specific information will really help

Thank you for your efforts. And please check that you are running debug flavor. On release it should run without that error.
I also tried with latest SDK version and with couple of fresh app installs, I could not reproduce it.

[androidacy-user]

Hello @androidacy-user
To inspect the issue in a detailed manner could you please share:

• your IDE and its version
• which android API are you trying with
• do you use some special flag with gradle? enableAssertions = true, -ea (or -enableassertions), or any other assert enable mechanism
• And other platform specific information will really help

Thank you for your efforts. And please check that you are running debug flavor. On release it should run without that error.
I also tried with latest SDK version and with couple of fresh app installs, I could not reproduce it.

Android studio 2025.x, standard Countly init(), absolutely not, every platform tested, both release and debug crash without workarounds.

[arifBurakDemiray]

Hello @androidacy-user

It’s difficult to determine the cause from the current information. To help us investigate further, could you please try the following:

• Create a fresh sample application (a new empty Android project).
• Integrate the Countly SDK there using the same setup steps you used in your main project.
• Check if the same issue occurs.

If the issue only happens in your main app, that would suggest it’s related to the integration, project setup, or local environment. If you can share a minimal reproducible example (small demo project or code snippet) where the problem appears, we’ll be able to look into it much faster.

Thank you for your help and patience! 🙏