wake-alarm/phone_app/lib/main.dart
Krzysztof kuhy Rudnicki 7a3b767075 Fix E2E unlock dialog and log publish errors
Since the material_ui bump the app supplied no framework
MaterialLocalizations, so crdt_sync_flutter's E2ePassphraseButton
showDialog crashed and the phone stayed locked. Nothing synced and the
PC fallback rang on 2026-11-16. The app now provides the localization
delegates. Publish failures now reach logcat in release builds.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WzxdWWfb63jncj9Lca2jeX
2026-11-16 08:30:35 +01:00

94 lines
4.3 KiB
Dart

// Framework material, for its MaterialLocalizations delegate only: material_ui
// ships its own MaterialLocalizations type, so crdt_sync_flutter's dialogs
// (framework `showDialog`) found none and threw a null check.
// ignore: deprecated_member_use, the only source of the framework delegate.
import 'package:flutter/material.dart' as fw show DefaultMaterialLocalizations;
import 'package:material_ui/material_ui.dart';
import 'package:wake_alarm_sync/screens/home_screen.dart';
import 'package:wake_alarm_sync/screens/ring_screen.dart';
import 'package:wake_alarm_sync/screens/session_screen.dart';
import 'package:wake_alarm_sync/services/alarm_policy.dart';
import 'package:wake_alarm_sync/services/alarm_scheduler.dart';
import 'package:wake_alarm_sync/services/day_pool_refresh.dart';
import 'package:wake_alarm_sync/services/headless_ring_start.dart';
import 'package:wake_alarm_sync/ui/app_name.dart';
import 'package:wake_alarm_sync/ui/theme.dart';
/// Route the Kotlin `AlarmActivity` hands to the engine as its initial
/// route.
const String kRingRoute = '/ring';
/// Navigator key, so the platform side can drive navigation without a context.
final GlobalKey<NavigatorState> navigatorKey = GlobalKey<NavigatorState>();
/// Entry point.
///
/// `ensureInitialized` is required before any MethodChannel call: the
/// startup re-arm below runs before the first frame.
Future<void> main() async {
WidgetsFlutterBinding.ensureInitialized();
// The alarm is not opt-in: launching the app is enough to arm it. There is
// no "set alarm" button to forget, and no cancel to reach for at 02:00 —
// AlarmPolicy fixes the time (the daily ramp, 08:00 down to 07:00) and
// only ever lets it move earlier.
final policy = await AlarmPolicy.load();
await AlarmScheduler().armSchedule(policy.hour, policy.minute);
runApp(const WakeAlarmSyncApp());
}
/// Headless entry point: the daily alarm starts it natively
/// (`HeadlessRingStart.kt`) to publish `ring_started` with no screen.
///
/// Lives here because only the root library's entry points are reachable
/// by name from Kotlin; `vm:entry-point` keeps release tree-shaking off it.
@pragma('vm:entry-point')
Future<void> ringStartedMain() => runHeadlessRingStart();
/// Headless entry point: `PoolSyncReceiver.kt` starts it in the evening and
/// shortly before the alarm, so a free or sick day marked on the PC reaches
/// the native ring-path caches with the app closed.
@pragma('vm:entry-point')
Future<void> poolSyncMain() => runHeadlessPoolSync();
/// Root application widget.
class WakeAlarmSyncApp extends StatelessWidget {
/// Creates a [WakeAlarmSyncApp]; [newScheduler] is the probes' seam.
const WakeAlarmSyncApp({super.key, this.newScheduler});
/// Builds the platform bridge for the ring and session screens.
///
/// Null in production (each screen builds the real one). The emulator
/// harness supplies a file-driven bridge so a machine with no NFC and no
/// step sensor can still walk the whole morning. A factory rather than an
/// instance so each screen owns its own, as in production: the NFC
/// listener's ownership is per instance, and sharing one instance hid the
/// ring-dispose-wipes-session-listener bug the phone had just shown.
final AlarmScheduler Function()? newScheduler;
@override
Widget build(BuildContext context) {
return MaterialApp(
title: kAppName,
theme: buildAppTheme(),
navigatorKey: navigatorKey,
localizationsDelegates: const <LocalizationsDelegate<dynamic>>[
fw.DefaultMaterialLocalizations.delegate,
DefaultWidgetsLocalizations.delegate,
],
// AlarmActivity sets its initial route to kRingRoute, so the ring screen
// is what comes up over the lockscreen; the launcher still gets home.
routes: <String, WidgetBuilder>{
'/': (_) => const HomeScreen(),
kRingRoute: (_) => RingScreen(scheduler: newScheduler?.call()),
// Reached by pushReplacement from the ring screen, or as
// AlarmActivity's initial route when the launcher or the ongoing
// notification reopens a live session (SessionNotice.kt). Always
// inside AlarmActivity: NFC reader mode and the kept-on screen live
// there.
kSessionRoute: (_) => SessionScreen(scheduler: newScheduler?.call()),
},
);
}
}