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

Aperta
  • Qualcosa non va?
#668 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, dart, flutter
Ambito
computer-graphics, mobile

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Dart
Stelle
1.5k
Fork
244
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di rive-app/rive-flutter

Tutte le issue di rive-app/rive-flutter

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.