lateinit property currentStep has not been initialized | Community
Skip to main content

Hi. 
We have a crash in our app when pushing a survey to some of our users. 
We are using version 17.1.0 (latest)

This is the crash log → 

io.intercom.android.sdk.survey.SurveyViewModel.buildContentState (SurveyViewModel.kt:215)

io.intercom.android.sdk.survey.SurveyViewModel.access$submitSurvey (SurveyViewModel.kt:83)

io.intercom.android.sdk.survey.SurveyViewModel.access$buildContentState (SurveyViewModel.kt:83)

io.intercom.android.sdk.survey.SurveyViewModel$submitSurvey$1.invokeSuspend (SurveyViewModel.kt:388)

kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:34)

kotlinx.coroutines.DispatchedTask.run (DispatchedTask.kt:100)

kotlinx.coroutines.internal.LimitedDispatcher$Worker.run (LimitedDispatcher.java:124)

kotlinx.coroutines.scheduling.TaskImpl.run (Tasks.kt:89)

kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely (CoroutineScheduler.java:586)

kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask (CoroutineScheduler.kt:820)

kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker (CoroutineScheduler.kt:717)

kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run (CoroutineScheduler.kt:704)

Hey there ​@Curwer, Emily here from Support Engineering at Intercom 👋🏼

 

The crash log points to SurveyViewModel.buildContentState (SurveyViewModel.kt:215) and is triggered during survey submission. The stack trace involves coroutine suspension and resumption, indicating the crash may be related to asynchronous state handling in the survey flow.

 

Although 17.1.1 does not explicitly mention a fix for this issue, it is always recommended to upgrade to the latest version, as minor bug fixes may not be fully documented. If the issue persists after upgrading the version, could you report it to our Intercom support with the detailed crash log? - you can reference this community question using the URL if you find that easier! 

 

If the crash is blocking, consider rolling back to a previous stable version of the SDK (e.g., 17.0.x) if you did not experience the issue there.

Terms & ConditionsAccessibility statement