You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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)
The text was updated successfully, but these errors were encountered:
Description
Rive assets with an artboard that leverages nested artboards have a couple of issues.
IOS
Android
Both Platforms
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)
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
)The text was updated successfully, but these errors were encountered: