Problems with using rive assets with nested art
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react-native, typescript
- Domain
- mobile-dev
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.
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)
- Dominant language
- TypeScript
- Stars
- 785
- Forks
- 81
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from rive-app/rive-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rive-app/rive-react-native#433 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
rive-app/rive-react-native#431 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
rive-app/rive-react-native#448 · 2 comments · 1 reaction ·
-
[Android] Rive events dispatched off the UI thread can deadlock with Reanimated under Fabric (ANR)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
rive-app/rive-react-native#444 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
rive-app/rive-react-native#441 ·
All issues in rive-app/rive-react-native
Similar issues
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
databendlabs/databend-docs#3511 ·
-
area/dashboard kind/bug QA/dev-automation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rancher/dashboard#19379 · 2 comments ·
Maintainers usually reply within 5 days
-
perf(core): getComments() runs the approved count and the comment list as two sequential queriesOpenarea/core bot:bug bot:working
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
emdash-cms/emdash#3905 · 2 comments ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 90/100
lingdojo/kana-dojo#31728 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
selective-claw: freshTailTurns=0 keeps ALL turns verbatim and summarizes none (slice(-0) === slice(0))Possibly taken @zjncs claimed this today. Opencomponent:tokenless
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
agentic-os-org/ANOLISA#6112 · 1 comment ·
Maintainers usually reply within 1 day