Chat-screen performance (customer + mitra): - Parent screens have zero `ref.watch` — only `ref.listen` for side effects - Body extracted into its own `ConsumerStatefulWidget`; AppBar parts split into narrow `.select` consumers (mode, sensitivity, timer) - Per-second timer ticks routed to dedicated providers (`chatRemainingSecondsProvider` + new `mitraChatRemainingSecondsProvider`) so WS `session_tick` frames don't invalidate the rest of the chat state Dispose-in-ref bug fix: - `home_screen.dart`, `payment_screen.dart`, `mitra_chat_screen.dart` — ref-using cleanup moved from `dispose()` to `deactivate()`. Modern Riverpod invalidates `ref` the moment `dispose()` runs; the resulting silent error corrupts the widget-tree finalize and the next screen appears frozen - `halo_lints` package added at repo root with `no_ref_in_dispose` rule to catch this pattern in CI / IDE analysis - `custom_lint` activated in both apps' `analysis_options.yaml` (was installed but never wired in — also brings `riverpod_lint`'s `avoid_ref_inside_state_dispose` online) - CLAUDE.md Pitfalls section added to client_app + mitra_app Phase 4 §3 retryable blast-failure (Option A): - Backend `expirePairingRequest` + all-rejected use `recordIntermediateFailure` instead of `failPaymentSession` so the payment session stays `confirmed` for re-blast - WS `pairing_failed` payload carries `is_terminal: false` on the retryable paths; client parses the flag and exposes `retryBlast()` - "Coba cari lagi" CTA on S7 Timeout now re-blasts on the same payment - Pairing service test updated to reflect the new semantics Customer waiting-payment screen navigation patch: - `_navigateTerminal` uses `Future.microtask` + `addPostFrameCallback` redundancy after a release-mode bug where polling stopped but `context.go` never fired, leaving the screen visually stuck on "menunggu pembayaran" See requirement/resume-2026-05-15.md for next-day pickup checklist (mitra release rebuild + S21 Ultra install + retest is the gating item). Bundles unrelated in-flight Phase 4 §2.x work that was already on disk (ESP screen removal, USP one-time gate scaffolding, bestie-availability public route, OTP service edits, Maestro flow tweaks) — kept together to avoid a partial-rebase mess. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
117 lines
3.7 KiB
Dart
117 lines
3.7 KiB
Dart
import 'dart:async';
|
|
|
|
import 'package:firebase_core/firebase_core.dart';
|
|
import 'package:firebase_messaging/firebase_messaging.dart';
|
|
import 'package:flutter/material.dart';
|
|
import 'package:flutter_riverpod/flutter_riverpod.dart';
|
|
import 'core/api/api_client_provider.dart';
|
|
import 'core/auth/auth_notifier.dart';
|
|
import 'core/auth/auth_providers_provider.dart';
|
|
import 'core/auth/token_storage.dart';
|
|
import 'core/chat/active_session_notifier.dart';
|
|
import 'core/chat/chat_notifier.dart';
|
|
import 'core/notifications/notification_service.dart';
|
|
import 'core/theme/halo_theme.dart';
|
|
import 'firebase_options.dart';
|
|
import 'router.dart';
|
|
|
|
void main() async {
|
|
WidgetsFlutterBinding.ensureInitialized();
|
|
|
|
// Pre-warm flutter_secure_storage. The first call triggers AndroidX
|
|
// Security MasterKey generation (RSA in Keystore) — fast on hardware-backed
|
|
// keystores but multi-second on emulator's software-emulated TEE. Kicking
|
|
// it off here in parallel with Firebase init hides the latency behind the
|
|
// splash instead of paying it on the user's first interaction.
|
|
unawaited(TokenStorage().readRefreshToken());
|
|
|
|
await Firebase.initializeApp(options: DefaultFirebaseOptions.currentPlatform);
|
|
|
|
final messaging = FirebaseMessaging.instance;
|
|
await messaging.requestPermission();
|
|
|
|
runApp(const ProviderScope(child: App()));
|
|
}
|
|
|
|
class App extends ConsumerStatefulWidget {
|
|
const App({super.key});
|
|
|
|
@override
|
|
ConsumerState<App> createState() => _AppState();
|
|
}
|
|
|
|
class _AppState extends ConsumerState<App> {
|
|
bool _fcmRegistered = false;
|
|
bool _authProvidersPreloaded = false;
|
|
|
|
@override
|
|
void initState() {
|
|
super.initState();
|
|
// Phase 4: preload server-driven auth-provider gating once on cold start.
|
|
// Cached via @Riverpod(keepAlive: true) — subsequent reads are instant.
|
|
WidgetsBinding.instance.addPostFrameCallback((_) {
|
|
if (_authProvidersPreloaded) return;
|
|
_authProvidersPreloaded = true;
|
|
ref.read(authProvidersProvider.future);
|
|
});
|
|
}
|
|
|
|
void _registerFcmToken() {
|
|
if (_fcmRegistered) return;
|
|
_fcmRegistered = true;
|
|
Future(() async {
|
|
try {
|
|
final token = await FirebaseMessaging.instance.getToken();
|
|
if (token != null) {
|
|
await ref.read(apiClientProvider).post('/api/shared/device-token', data: {'token': token});
|
|
}
|
|
} catch (_) {
|
|
_fcmRegistered = false;
|
|
}
|
|
});
|
|
}
|
|
|
|
@override
|
|
Widget build(BuildContext context) {
|
|
// FCM registration on auth.
|
|
ref.listen(authProvider, (prev, next) {
|
|
final data = next.valueOrNull;
|
|
if (data is AuthAuthenticatedData || data is AuthAnonymousData) {
|
|
_registerFcmToken();
|
|
} else {
|
|
// Logged out (or initial) — ensure the chat WS is closed.
|
|
ref.read(chatProvider.notifier).disconnect();
|
|
}
|
|
});
|
|
|
|
// Global chat WebSocket lifecycle: connect whenever the user has an
|
|
// active session, regardless of which screen is mounted. The chat screen
|
|
// only joins this connection — it doesn't own it. FCM remains the
|
|
// background-only fallback.
|
|
ref.listen(activeSessionProvider, (prev, next) {
|
|
final snapshot = next.valueOrNull;
|
|
final notifier = ref.read(chatProvider.notifier);
|
|
if (snapshot == null || !snapshot.hasSession) {
|
|
if (notifier.connectedSessionId != null) {
|
|
notifier.disconnect();
|
|
}
|
|
return;
|
|
}
|
|
final sessionId = snapshot.sessionId;
|
|
if (sessionId != null && notifier.connectedSessionId != sessionId) {
|
|
notifier.connectIfNotConnected(sessionId);
|
|
}
|
|
});
|
|
|
|
final router = ref.watch(routerProvider);
|
|
|
|
NotificationService.initialize(router);
|
|
|
|
return MaterialApp.router(
|
|
title: 'Halo Bestie',
|
|
theme: haloThemeData(),
|
|
routerConfig: router,
|
|
);
|
|
}
|
|
}
|