From a8c06175915ed70b7a00e5d00a8b9f35f7520e97 Mon Sep 17 00:00:00 2001 From: Your Name Date: Tue, 22 Sep 2026 10:23:00 +0200 Subject: [PATCH] After correcting the countdown on mobile version2 --- .../prediction/presentation/prediction_screen.dart | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/prediqo_mobile/lib/features/prediction/presentation/prediction_screen.dart b/prediqo_mobile/lib/features/prediction/presentation/prediction_screen.dart index b603b666..d1289abd 100644 --- a/prediqo_mobile/lib/features/prediction/presentation/prediction_screen.dart +++ b/prediqo_mobile/lib/features/prediction/presentation/prediction_screen.dart @@ -155,11 +155,14 @@ class _PredictionScreenState extends State { children: [ Row( children: [ - _StatusChip( - round != null - ? serverAdjustedCountdown(round).effectiveStatus - : 'waiting', - ), + // Web parity: `round.status` is already the authoritative, + // baked-in effective status (see `mergeRound` / + // `_withEffectiveStatus`). Re-deriving it here from a second, + // independent `DateTime.now()` clock (out of sync with + // `_LiveCountdown`'s own ticking clock below) is exactly what + // caused the badge and the big countdown number to briefly + // disagree. Trust the single source of truth instead. + _StatusChip(round?.status ?? 'waiting'), const Spacer(), if (round != null) _LiveCountdown(