CCExtractor / CCExtractor/ultimate_alarm_clock

Bug: Incorrect await usage in TimerRingController causes build failure & possible crash

Abierto
#854 2 comentarios 0 reacciones 0 asignados Ver en GitHub
bug
Lenguaje dominante
Dart
Estrellas
112
Forks
227
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Description

The TimerRingController misused await and accessed properties on a Future, leading to compile-time errors and a potential null crash.

- Problematic lines:
AudioUtils.playTimer(alarmRecord: await getFakeTimerModel().value); // `.value` on a Future
AudioUtils.stopTimer(ringtoneName: await getFakeTimerModel().ringtoneName); // property access before await
vibrationTimer!.cancel(); // potential null crash

- Impact:
Build fails with type/property errors.
Possible runtime crash if vibrationTimer is null.

What I tried
Reproduced by launching a timer ring; build failed due to the incorrect .value and property access on a Future. Verified crash risk by inspecting vibrationTimer.

### Screenshots

_No response_

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.