fix(android): defer autoplay until after VM instance is bound#283
Merged
Conversation
mfazekas
force-pushed
the
fix/android-autoplay-before-databind
branch
from
June 3, 2026 07:51
7646d10 to
c67eebb
Compare
Entry transitions evaluated with default VM values before the user's instance was bound. Use settleInitialState=false when data binding is active so the state machine is created without advancing, then bind, then let the Choreographer frame advance with correct values. Also bumps rive-android from 11.4.0 to 11.6.1.
mfazekas
force-pushed
the
fix/android-autoplay-before-databind
branch
from
June 5, 2026 12:55
c67eebb to
dee54da
Compare
mfazekas
enabled auto-merge (squash)
June 5, 2026 14:31
HayesGordon
approved these changes
Jun 8, 2026
mfazekas
pushed a commit
that referenced
this pull request
Jun 8, 2026
🤖 I have created a release *beep* *boop* --- ## [0.4.11](v0.4.10...v0.4.11) (2026-06-08) ### Bug Fixes * **android:** defer autoplay until after VM instance is bound ([#283](#283)) ([f600a47](f600a47)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #282
When
dataBindandautoPlayare both active, Entry transitions evaluated with default VM values before the user's instance was bound. Now only in that case we passautoplay=false, autoBind=falsetosetRiveFileand callplay(settleInitialState=false)so the state machine is created without advancing Entry. The first Choreographer frame advances with the user's VM instance already bound. All other cases (autoPlay={false}, no data binding) keep the original behavior.Also bumps rive-android from 11.4.0 to 11.6.1.
Reproducer: https://rive.app/community/files/27852-52628-on-entry-actions-reproducer
Test plan
entry-databinding.harness.tsxsetsinput=42via VM instance, mounts withautoPlay=true+dataBind, assertsinputOnEntry=42(Entry copiedinputintoinputOnEntry)inputOnEntrystayed at default-100)