Repository navigation
fix(android): bump rive-android to 11.6.2 - #317
Merged
Merged
Conversation
1 task
11.6.2 backports the ViewModelInstance read/write lock from 11.7.0 (without the 11.7.x Vulkan default flip). In 11.6.1, state-machine advance holds the file lock but ViewModelInstance property access takes no lock, so a property write or instance teardown on another thread can race the advance path's DataBindContainer::updateDataBinds and crash.
mfazekas
force-pushed
the
fix/android-rive-11.6.2
branch
from
July 6, 2026 05:12
a88afa2 to
89378b3
Compare
mfazekas
enabled auto-merge (squash)
July 6, 2026 11:44
HayesGordon
approved these changes
Jul 6, 2026
mfazekas
pushed a commit
that referenced
this pull request
Jul 6, 2026
🤖 I have created a release *beep* *boop* --- ## [0.4.14](v0.4.13...v0.4.14) (2026-07-06) ### Bug Fixes * **android:** bump rive-android to 11.6.2 ([#317](#317)) ([ae66b24](ae66b24)) * **android:** don't re-acquire a disposed Rive file on view re-attach ([#319](#319)) ([4259723](4259723)) * **hooks:** no-op stale property setter calls after dispose ([#316](#316)) ([dbb4dd7](dbb4dd7)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This was referenced Jul 6, 2026
mfazekas
added a commit
that referenced
this pull request
Jul 7, 2026
Merges `main` up to the 0.4.14 release into the iOS experimental branch. No conflicts. Notable changes pulled in: 1. fix(android): don't re-acquire a disposed Rive file on view re-attach (#319) 2. fix(hooks): no-op stale property setter calls after dispose (#316) 3. fix(android): bump rive-android to 11.6.2 (#317) — resolves to 11.6.2 here (up from 11.6.1) On the #319 native fix: this branch has the legacy/new Android backend split, so git's rename detection applied the fix to the `android/src/legacy` variant of `RiveReactNativeView.kt` — which is correct, since the crash is a property of upstream `RiveAnimationView`'s cached `rendererAttributes.resource`. The `android/src/new` backend is a separate `TextureView`/`CommandQueue` implementation with no such code path, so the same tweak neither applies nor is needed there. A re-attach lifecycle bug in the new backend, if any, would be a separate fix. --------- Co-authored-by: Rive Engineering <60802183+rive-engineering@users.noreply.github.com>
mfazekas
added a commit
that referenced
this pull request
Jul 14, 2026
Bumps the pinned native runtimes to the latest releases: rive-android 11.6.2 → 11.7.1 and rive-ios 6.20.4 → 6.21.0. Notable changes on Android: 11.7.0 enables the Vulkan renderer by default (#317 had intentionally stayed on the 11.6.2 backport to defer this) and includes the full ViewModelInstance read/write lock. 11.7.1 adds serialized touch-triggered advances and mipmap generation fixes. Notable changes on iOS: 6.21.0 adds VoiceOver semantics support, artboard volume control, and defaults `RiveUIView.isOpaque` to false so transparent backgrounds render correctly.
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
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.
Bumps the pinned Android runtime from 11.6.1 to 11.6.2, which backports the ViewModelInstance read/write lock from 11.7.0. A patch bump carries just the lock; the 11.7 minor also ships the new Vulkan backend (opt-in — OpenGL stays the default renderer) plus other changes, and grows
librive-android.soby ~2 MB per ABI (arm64: 5.76 → 7.73 MB uncompressed, +34%) since Vulkan is compiled into the prebuilt library even when unused.In 11.6.1,
StateMachineInstance.advance()holds the file lock but ViewModelInstance property access takes no lock, so a property write or instance teardown on another thread can race the advance path'sDataBindContainer::updateDataBindsand crash (SIGSEGV reported in production on 0.4.11). Related ledger: #308.Verified on a Pixel 6 API 34 emulator (arm64 debug build): the databinding-related harness suites and a targeted advance-vs-write stress loop are green on both 11.6.1 and 11.6.2 (the race did not reproduce locally at this volume; no regressions from the bump).