asyncupdate have a crash

[FeanCheng]

java.lang.IllegalStateException: The specified message queue synchronization barrier token has not been posted or has already been removed.

[FeanCheng]

I quickly switched between multiple Lotties, and this problem was triggered.
Lottie version : last version

[gpeal]

This stack trace doesn't flow through any Lottie code so it may be either unrelated to Lottie or something out of Lottie's control on your phone or version of Android.

Is this reliably reproducible? If so, can you create a project that reproduces this?

[FeanCheng]

Okay, perhaps I need some time to try to reproduce it as much as possible.

[Fylan0]

Okay, perhaps I need some time to try to reproduce it as much as possible.

Hello, I encountered the same exception after using two Lottie animations in my project. However, I tried to reproduce it but couldn’t, so I’m not sure what caused it. Did you manage to locate the issue?

v6.4.1

[Fylan0]

I used the code from the sample。
app:lottie_asyncUpdates="enabled"

It can cause an ANR or the exception.

[gpeal]

@Fylan0 Can you be more specific with your repro steps?

[gpeal]

@Fylan0 ANRs and exceptions are also two different things. Which one are you encountering? Can you include a bugreport/stacktrace for either?

[rluick15]

Don't have much data to add, but we are also seeing this crash happen occasionally on 6.5.0. Only occurs with async updates enabled. QA team was occasionally able to reproduce and we saw in prod as well, had a remote toggle to disable the async updates and that resolved the issue for us.

[gpeal]

@rluick15 Are there any trends? Android versions, etc? I've tried to reproduce this but I'm unable to.

[kozaxinan]

We also have this our app. We recently updated to 6.6.7 and enabled async updates. It happens in a screen that has multiple animations. lottie animation is controlled like following.

     private const val PIN_ANIMATION_START = 0f
        private const val PIN_ANIMATION_MIDDLE = 0.4f
        private const val PIN_ANIMATION_END = 0.9f

mapFragment.apply {
            doOnTouchDown {
                startPinAnimation()
                viewModel.onMapDragStarted()
                closeSuggestions()
            }
            doOnTouchUp {
                stopPinAnimation()
                viewModel.onMapDragFinished()
            }
        }

private fun startPinAnimation() {
        binding.pinLottieAnimationView.cancelAnimation()
        binding.pinLottieAnimationView.setMinAndMaxProgress(PIN_ANIMATION_START, PIN_ANIMATION_MIDDLE)
        binding.pinLottieAnimationView.playAnimation()
    }

    private fun stopPinAnimation() {
        binding.pinLottieAnimationView.cancelAnimation()
        binding.pinLottieAnimationView.setMinAndMaxProgress(PIN_ANIMATION_MIDDLE, PIN_ANIMATION_END)
        binding.pinLottieAnimationView.playAnimation()
    }

based on map location there is also another loading animation. When I create stress with lot of touch events, I can reproduce locally.

When issue occurs, other animation on main thread stops, buttons become unresponsive, but map and bottom sheet still work. (Interestingly) Lottie animation still works.

I can reproduce locally but I still don't have why and how it reproduce.

Disabling async updates prevents the crash.

other animations on the screen AnimatedVectorDrawableCompat, AlphaAnimation