Rendering issue with 11.7.0

[laurentvoodoo]

Submission checklist

• I have confirmed the issue is present in the latest version of rive-android
• I have searched the documentation and forums and could not find an answer
• I have searched existing issues and this is not a duplicate

Description

This attached rive works in version from 11.3.1 to 11.6.1, but failed with new version 11.7.0

Previous working version

11.6.1

Reproduction steps / code

val resources = LocalResources.current
val worker = rememberRiveWorker()
val source = remember { RiveSource.Raw(R.raw.partner_intro)}
val riveResource = remember { RiveFileSource.RawRes(source.resId, resources)}
val riveFile = rememberRiveFile(riveResource, worker)
Rive(
    modifier = Modifier,
    file = riveFile,
    playing = true,
    fit = Fit.Contain(),
    pointerInputMode = RivePointerInputMode.PassThrough
)

Upload your reproduction files / stack trace

No response

Source .riv / .rev file

partner_intro.zip

Screenshots / video

test.mp4

Rive Android runtime version

11.7.0

Rive API

Compose

Device

Samsung A32

Device OS

Android 13

App minimum SDK level

29

App target SDK level

36

App NDK level

No response

Other Rive runtimes affected

No response

Dependencies with native libraries

Unity

Additional context

No response

[sebastian-gallese-speak]

Confirming the same regression — renders on 11.6.1, blank on 11.7.0 (same app, only the runtime changed).

A few data points that may help narrow it down:

• Reproduces on a physical device and an emulator (Pixel, API 36, ARM64).
• On the emulator it's blank in every GPU mode — Vulkan/MoltenVK, Vulkan off (lavapipe), and -gpu swiftshader — so it's not tied to one backend.
• Happens with both the Compose Rive() API and the view-based RiveAnimationView, using the default renderer.

Looks like a renderer regression in 11.7.0 itself. Happy to share a minimal repro.

[laurentvoodoo]

Version 1.7.2 fix the issue for me.
Is it also ok for you @sebastian-gallese-speak ?

[ErikUggeldahl]

Thanks for checking and confirming 11.7.2 fixes the issue for you, @laurentvoodoo. @sebastian-gallese-speak if you could confirm that it fixes it for you as well, I'll close it out.