CCExtractor / CCExtractor/ultimate_alarm_clock
Bug: Incorrect await usage in TimerRingController causes build failure & possible crash
- Vorherrschende Sprache
- Dart
- Sterne
- 112
- Forks
- 227
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### 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_
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.