Skip to content

[Android] New runtime renders transparent artboard areas black #409

Closed

Description

@maksym-kovalchuk-liven

Submission checklist

  • I have confirmed the issue is present in the latest version of @rive-app/react-native
  • 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

On the new (default) Android backend, transparent areas of an artboard render black instead of showing the views behind the RiveView. It reproduces in both debug (Metro) and release builds. The legacy Android backend and iOS render the same files transparently.

Cause

The new backend's RiveReactNativeView renders into a TextureView that is never marked non-opaque. A TextureView treats its content as opaque by default, so the transparent clear colour is composited as black.

rive-android's own hosts set this flag: both the Compose Rive composable and RiveTextureView (which the legacy backend uses through RiveAnimationView) set isOpaque = false.

Possible solution

Set isOpaque = false on the TextureView in android/src/new/java/com/rive/RiveReactNativeView.kt:

   private val textureView = TextureView(context).apply {
+    isOpaque = false
     layoutParams = LayoutParams(LayoutParams.MATCH_PARENT, LayoutParams.MATCH_PARENT)

Happy to open a PR.

Previous working version

Legacy Android backend (0.4.x, or 0.5.x with USE_RIVE_LEGACY)

Reproduction steps / code

Render any artboard without a background fill over a non-black background on Android with the default (new) backend, in a debug or a release build.

@rive-app/react-native version

0.5.1 (the code is unchanged in 0.5.3 and on main)

Platform

Android only

React Native version

0.86.2

Expo setup

Yes — Expo prebuild / EAS Build

Expo SDK version (if applicable)

57.0.11

Android device & OS version (if applicable)

Android Emulator — API 36

Activity

  1. mfazekas commented on Oct 7, 2026

    @mfazekas
    Collaborator

    Thanks for the report and the diagnosis! Reproduced it and confirmed your fix; it's in #410 and will ship in the next 0.5.x release.

  2. added a commit that references this issue on Oct 7, 2026
    d64f679
  3. mfazekas commented on Oct 7, 2026

    @mfazekas
    Collaborator

    Correction: the fix will land via #411 instead of #410, same change.

  4. added a commit that references this issue on Oct 7, 2026
  5. added a commit that references this issue on Oct 13, 2026
    029fab1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    androidbugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions