rive-app / rive-app/rive-android
RiveUI composable's state machine is settled on activity resume
Open
Nobody has claimed this yet.
triage
- Dominant language
- Kotlin
- Stars
- 538
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
Description
CommandQueue's onStateMachineSettled is called when the activity restores, which leads to all rive elements on the screen pausing until they're interacted with by the user.
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 by tracing CommandQueue.onStateMachineSettled through the activity resume and restoration lifecycle in the Android runtime. Reproduce the pause of all Rive elements after restoration, then identify why settlement is triggered there; done means animations resume without requiring user interaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100