[Bug] .riv file behavior inconsistency after upgrading from 9.11.3 to 11.1.0

Description

Our team recently attempted to upgrade the Rive Android SDK from version 9.11.3 to 11.1.0. After completing the upgrade, we performed regression testing on our existing .riv files and discovered that one particular .riv file behaves inconsistently compared to the previous version.

Expected Interaction Flow

The .riv file in question has the following interaction flow:

1. Upon loading the .riv file, three ingredient items appear with entrance animations: shrimp, mushroom, and sausage.
2. After triggering interactive_start, the user can begin interacting with the elements.
3. All three ingredients are draggable. When dragging, a snap zone indicator appears. If an ingredient is dropped in the wrong position, it automatically returns to its original location.
4. Once all three ingredients are dragged to their correct positions, they disappear and the interaction flow completes.

Observed Issue (SDK v11.1.0)

In the new SDK version, the shrimp ingredient does not disappear when dragged to the correct snap zone. Instead, it returns to its original position — a behavior that should only occur when the drop position is incorrect.

Additionally, the shrimp eventually disappears along with the other two ingredients after they are correctly placed.

The other two ingredients (mushroom and sausage) work as expected.

Attachments

• Minimal reproducible Android Studio demo project: Google Drive Link
• Video: Correct interaction flow (SDK v9.11.3): Google Drive Link
• Video: Incorrect behavior (SDK v11.1.0): Google Drive Link
• Rive project file (.rev): Google Drive Link

Environment

• Rive Android SDK version (working): 9.11.3
• Rive Android SDK version (broken): 11.1.0

Start with the linked minimal reproducible Android Studio demo and compare the .riv interaction under SDK 9.11.3 and 11.1.0. Use the provided videos and Rive project file to confirm the shrimp's incorrect snap behavior; done means all three ingredients disappear when dropped in their correct zones under the newer SDK.