rive-app / rive-app/rive-react-native
Problems with using rive assets with nested art
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 783
- Forks
- 81
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 3
Description
Description
Rive assets with an artboard that leverages nested artboards have a couple of issues.
IOS
- Scrolling on lists is not as smooth (best perceived when slowly scrolling)
Android
- Click events are not firing nearly as often as they should be
- Can not hold and keep buttons depressed (possibly related)
Both Platforms
- Nodes below the fold (likely those caught in virtualization) sometimes don't have their inputs set.
These problems are not observed with rive assets that don't use nested artboards or when directly using the nested artboard as opposed to the parent artboard.
None of these issues exist on web either.
Provide a Repro
https://github.com/GibbyBox/repro-nested-artboard-native-issues
Source .riv/.rev file
.riv committed in repro
ui_nodes.rev.zip
Device & Versions (please complete the following information)
- Device: Iphone 15 Pro Max, Google Pixel 7a
- OS: iOS 18.3.1, Android API level 34
- NPM Version: 10.5.2
Additional Context
The provided repro has two tabs - one where I use the parent artboard and one where I instead use the nested artboard. I've also tested and can confirm this issues exists on all rive rendering engines (can be configured in useSetRiveRenderer.ts)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked repro, comparing its parent-artboard and nested-artboard tabs across iOS and Android. Read useSetRiveRenderer.ts and investigate the reported scrolling, click, button-state, and virtualized-node input behavior. Done means the listed issues no longer reproduce with nested art assets on the affected native platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100