Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Problems with using rive assets with nested art

未关闭
#296 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
react-native, typescript
领域
mobile-dev

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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)

主要语言
TypeScript
星标
785
派生
81
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

rive-app/rive-react-native 的其他 Issue

查看 rive-app/rive-react-native 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。