CoroutineLiveData triggers cancel on not already cancelled block [157840298]

Fixed

Bug

Status Update

No update yet.

Description

sk...@gmail.com

created issue #1

Jun 1, 2020 11:55AM

Component used:
androidx.lifecycle:lifecycle-livedata-ktx
androidx.lifecycle:lifecycle-runtime
androidx.lifecycle:lifecycle-runtime-ktx
androidx.lifecycle:lifecycle-livedata-ktx
androidx.lifecycle:lifecycle-viewmodel-ktx
androidx.lifecycle:lifecycle-common-java8

Version used: 2.3.0-alpha02
Devices/Android versions reproduced on: OnePlus6T, Samsungs, Xiaomis, etc.

We are using Flow.asLiveData() converter. We receive java.lang.IllegalStateException: Cancel call cannot happen without a maybeRun exceptions on production. Unable to reproduce locally. Seems like some race condition is happening in LiveData.

androidx.lifecycle.BlockRunner.cancel (CoroutineLiveData.kt:184)
androidx.lifecycle.CoroutineLiveData.onInactive (CoroutineLiveData.kt:245)
androidx.lifecycle.LiveData$ObserverWrapper.activeStateChanged (LiveData.java:440)
androidx.lifecycle.LiveData$LifecycleBoundObserver.onStateChanged (LiveData.java:395)
androidx.lifecycle.LifecycleRegistry$ObserverWithState.dispatchEvent (LifecycleRegistry.java:361)
androidx.lifecycle.LifecycleRegistry.forwardPass (LifecycleRegistry.java:300)
androidx.lifecycle.LifecycleRegistry.sync (LifecycleRegistry.java:339)
androidx.lifecycle.LifecycleRegistry.moveToState (LifecycleRegistry.java:145)
androidx.lifecycle.LifecycleRegistry.handleLifecycleEvent (LifecycleRegistry.java:131)
androidx.fragment.app.Fragment.performStart (Fragment.java:2934)
androidx.fragment.app.FragmentStateManager.start (FragmentStateManager.java:539)
androidx.fragment.app.FragmentManager.moveToState (FragmentManager.java:1278)
androidx.fragment.app.FragmentManager.moveToState (FragmentManager.java:1417)
androidx.fragment.app.FragmentManager.moveFragmentToExpectedState (FragmentManager.java:1495)
androidx.fragment.app.FragmentManager.moveToState (FragmentManager.java:1548)
androidx.fragment.app.FragmentManager.dispatchStateChange (FragmentManager.java:2796)
androidx.fragment.app.FragmentManager.dispatchStart (FragmentManager.java:2752)
androidx.fragment.app.FragmentController.dispatchStart (FragmentController.java:262)
androidx.fragment.app.FragmentActivity.onStart (FragmentActivity.java:560)
androidx.appcompat.app.AppCompatActivity.onStart (AppCompatActivity.java:201)
com.***.BaseActivity.onStart (BaseActivity.kt:144)
android.app.Instrumentation.callActivityOnStart (Instrumentation.java:1342)
android.app.Activity.performStart (Activity.java:7278)
android.app.Activity.performRestart (Activity.java:7419)
android.app.Activity.performResume (Activity.java:7432)
android.app.ActivityThread.performResumeActivity (ActivityThread.java:3780)
android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3845)
android.app.ActivityThread$H.handleMessage (ActivityThread.java:1773)
android.os.Handler.dispatchMessage (Handler.java:106)
android.os.Looper.loop (Looper.java:164)
android.app.ActivityThread.main (ActivityThread.java:7000)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:441)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1408)

Comments

sk...@gmail.com <sk...@gmail.com> #2Jun 1, 2020 11:57AM

I have the same issue.

yb...@google.com <yb...@google.com> Jun 1, 2020 05:19PM

Reassigned to yb...@google.com.

b9...@gmail.com <b9...@gmail.com> #3Jun 3, 2020 08:22AM

Here too!

yb...@google.com <yb...@google.com> #4Jun 3, 2020 09:53PM

yb...@google.com <yb...@google.com> #5Jun 3, 2020 09:59PM

the same for Java buildSrc

yb...@google.com <yb...@google.com> #6Jun 4, 2020 12:53AM

Same here

sk...@gmail.com <sk...@gmail.com> #7Jun 4, 2020 05:54AM

b9...@gmail.com <b9...@gmail.com> #8Jun 4, 2020 05:55AM

Any status update on this?

yb...@google.com <yb...@google.com> #9Jun 4, 2020 04:18PM

ap...@google.com <ap...@google.com> #10Jun 5, 2020 11:26AM

3.5 Canary 6 has same issue

yb...@google.com <yb...@google.com> Jun 5, 2020 03:13PM

Marked as fixed.

an...@gmail.com <an...@gmail.com> #11Jun 16, 2020 02:45PM

I got the same issue today if you it is related to the ne experimental feature "Only sync the active variant" introduced in Android Studio 3.3.
It's enabled by default...
On macOS you can disable it by going to "Android Studio" -> "Preferences" -> "Experimental"

yb...@google.com <yb...@google.com> #12Jun 16, 2020 06:33PM

Is this still being worked on?

an...@gmail.com <an...@gmail.com> #13Jun 17, 2020 08:44PM

Yes, the fix will be included in the next canary release of Studio 3.5.

an...@gmail.com <an...@gmail.com> #14Jun 17, 2020 09:12PM

Fix included in Studio 3.5 canary 12.

yb...@google.com <yb...@google.com> #15Jun 17, 2020 09:24PM

Disappointed this didn't make it into 3.4

an...@gmail.com <an...@gmail.com> #16Jun 17, 2020 10:47PM

I tried 3.3.4 rc 3 and 3.3.5 canary 10 unfortunately both of them has same problem

yb...@google.com <yb...@google.com> #17Jun 18, 2020 03:43AM

Seems like we have to wait for stable release of 3.5 to use this feature again

an...@gmail.com <an...@gmail.com> #18Jun 18, 2020 10:07AM

Is this why I am getting a lot of lint warnings in my .kt file?

an...@gmail.com <an...@gmail.com> #19Jun 18, 2020 10:58AM

Autocomplete still doesn't work in Studio 3.5 canary 12 (checked in project attached above and in own custom project)

yb...@google.com <yb...@google.com> #20Jun 18, 2020 05:11PM

an...@gmail.com <an...@gmail.com> #21Jun 19, 2020 11:11PM

Thank you for the feedback. We're currently working it.

fi...@colendi.com <fi...@colendi.com> #22Jun 8, 2021 06:47PM

Autocomplete doesn't work on 3.4, too.

Message last modified on Jun 8, 2021 06:57PM