fix: bump rive-android to 11.9.1 and rive-ios to 6.23.1 - #367
Merged
Conversation
Bumps the pinned native runtimes to the latest releases: rive-android 11.7.2 -> 11.9.1 and rive-ios 6.21.1 -> 6.23.1. On Android, 11.8.0 removed CommandQueue.settledFlow and 11.9.0 restored it as a deprecated shim, so the settling observer behind onStop keeps working under a suppression. 11.9.0 also tightens resource lifetime contracts (operations on closed resources now throw RiveResourceClosedException synchronously) and adds clearing of image properties. On iOS, 6.22.0 adds view-model instance names, 6.23.0 fixes data bindings in some state-machine files plus Metal validation errors when rendering images, and 6.23.1 makes runtime assertions debug-only.
HayesGordon
approved these changes
Aug 19, 2026
mfazekas
added a commit
that referenced
this pull request
Aug 19, 2026
Ports the runtime bump from #367 to the stable 0.4.x line: rive-android 11.7.2 → 11.9.1 and rive-ios 6.21.1 → 6.23.1. Only `package.json` needs changing here. The other two files in #367 (`android/src/new/...` and `ios/new/RiveRuntimeLogger.swift`) arrived with the breaking `feat!: experimental Rive runtime backend` (#134) that started the 0.5.0-beta line, so they don't exist on this branch. Also points this branch's copy of the release-please workflow at `release-v0.4`. Without `target-branch` the action reads its config and manifest from the repository's default branch and would cut a 0.5.0-beta; a push only ever triggers the workflow file on the branch pushed, so `main` keeps producing betas unchanged. The branch was cut from `v0.4.19`, which already carries a non-prerelease release-please config and a manifest at `0.4.19`, so no config changes were needed. Merging this should produce a `0.4.20` release PR, and a non-prerelease GitHub release publishes to the npm `latest` tag via the existing conditional in `publish.yml`. On verification, I could not get a green local run on this branch — but nothing I found is attributable to the bump, and each failure reproduces identically at the old pins: 1. The iOS example does not build on Xcode 26.5: RN 0.79's bundled fmt 11.0.2 hits the `consteval` error in `Pods/fmt/include/fmt/format-inl.h`. `main` carries a Podfile fix for this that this branch predates. Confirmed pre-existing by a clean `pod install` + build with RiveRuntime pinned back to 6.21.1 — identical errors. 2. `viewmodel-properties › non-existent properties return undefined` fails. Confirmed pre-existing at rive-android 11.7.2 — identical failure. 3. The Android emulator dies mid-run (`bad color buffer handle`, a gfxstream host-GPU crash), taking ~10 suites down with `adb` errors rather than assertion failures. Reproduced at 11.7.2 as well, on a cold-booted emulator. What did verify cleanly: Android compiles against 11.9.1 with zero deprecation warnings (this tree predates the API surface 11.9.x deprecates), and `pod install` resolves RiveRuntime 6.23.1. CI is the meaningful gate here, since it runs a different Xcode and emulator image.
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.
Bumps the pinned native runtimes to the latest releases: rive-android 11.7.2 → 11.9.1 and rive-ios 6.21.1 → 6.23.1.
On Android, 11.8.0 removed
CommandQueue.settledFlowand 11.9.0 restored it as a deprecated shim (removal planned for 12.0), so the settling observer behindonStopkeeps working under a@Suppress("DEPRECATION"). 11.9.0 also tightens resource lifetime contracts — operations on closed resources now throwRiveResourceClosedExceptionsynchronously instead of failing generically — and adds clearing of image properties. On iOS, 6.22.0 adds view-model instance names, 6.23.0 fixes data bindings in some state-machine files plus Metal validation errors when rendering images, and 6.23.1 makes runtime assertions debug-only.11.9.x also deprecates a batch of APIs the new Android backend still calls (
fromFile→create,createStateMachineByName→createStateMachineByNameConfirmed), all slated for removal in 12.0. Those are compile warnings only; migrating them is left as a follow-up.Verified locally: harness suites pass on both backends on both platforms (iOS 28/28 suites, 208 tests; Android new backend 28/28, 208 tests; Android legacy 28/28 after retrying two suites that flaked on the 1000 ms mount timeout, the same flake CI retries for). iOS example builds clean against 6.23.1 with both the new and legacy podspec paths, and jest, typecheck, eslint and ktlint are clean.