CCExtractor / CCExtractor/ultimate_alarm_clock

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

Aperta
#854 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub
bug
Lingua principale
Dart
Stelle
112
Fork
227
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

### 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_

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.