[Android][FCNT] IMGeglMakeCurrent crash on affected devices – Will the rive-android #468 fix be ported to rive-flutter?

Abierto
  • ¿Algo no está bien?
#668 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, dart, flutter
Área
computer-graphics, mobile

Línea de trabajo

Read the linked rive-android issue #468 and fix commit ff0d95c402ecfe5a5443e76e3c98b8ba0dd4b8f4 to understand the Android rendering workaround. Then trace the corresponding renderer path in rive-flutter or rive_native and check how affected FCNT devices select a backend. Done means affected devices render animations without the IMGeglMakeCurrent crash; the issue does not name relevant files or tests.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

known
Submission checklist
  • I have confirmed the issue is present in the latest version of the rive Flutter package
  • 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

We are experiencing a native Android crash related to Rive animation rendering on specific FCNT devices running Android 16.

The crash appears to be related to IMGeglMakeCurrent in the OpenGL driver.

This issue has already been reported and addressed in the Android Rive runtime:

Issue: https://github.com/rive-app/rive-android/issues/468
Fix commit: https://github.com/rive-app/rive-android/commit/ff0d95c402ecfe5a5443e76e3c98b8ba0dd4b8f4

The Android runtime fix disables OpenGL on affected FCNT firmware and uses Vulkan or Canvas as an alternative rendering backend.

We would like to know whether a corresponding fix is planned for the Flutter runtime (rive / rive_native).

Affected Devices

We have identified the issue on the following devices running Android 16:

Manufacturer Model
FCNT F-52E
FCNT FCG02
FCNT A402FC
FCNT M07

Current Workaround

As a temporary workaround, we detect the affected devices and disable Rive animations to prevent crashes.

However, we would prefer to restore animations once the underlying rendering issue is resolved.

Expected Behavior

Rive animations should render correctly on affected FCNT devices without causing native OpenGL crashes.

Questions

Is the fix from rive-android (#468 / commit ff0d95c) planned to be incorporated into rive-flutter / rive_native?
Does the Flutter runtime use the same OpenGL rendering path affected by this issue?
If a fix is planned, is there an estimated release version or timeline?

Thank you for your support!

Reproduction steps / code

No response

Upload your reproduction files / stack trace

No response

Source .riv / .rev file

No response

Screenshots / video

No response

Rive Flutter package version

0.14.11

Flutter version

Flutter 3.47.8

Device

FCNT F-52E

OS version

Android 16 Only

Additional context

No response

Lenguaje dominante
Dart
Estrellas
1.5k
Forks
244
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de rive-app/rive-flutter

Todos los issues de rive-app/rive-flutter

Issues similares

Más issues de Dart

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.