Flutter Android中如何在Hive存储FCM后台通知数据？

1. 规范FCM后台消息处理逻辑 #

FCM的Data Message需要在独立隔离区的FirebaseMessagingBackgroundHandler中处理，这个handler必须是顶级函数，且要确保Firebase初始化完成：

@pragma('vm:entry-point')
Future<void> firebaseMessagingBackgroundHandler(RemoteMessage message) async {
  // 后台隔离区中需重新初始化Firebase
  await Firebase.initializeApp();
  // 后续执行存储操作
}

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();
  // 注册后台消息处理器
  FirebaseMessaging.onBackgroundMessage(firebaseMessagingBackgroundHandler);
  runApp(MyApp());
}

2. 适配存储插件的隔离区兼容性 #

多数常用存储插件（如shared_preferences）依赖主UI线程上下文，无法在隔离区直接使用，可选择两种方案：

• 改用支持隔离区的存储库（如Hive）：

  @pragma('vm:entry-point')
  Future<void> firebaseMessagingBackgroundHandler(RemoteMessage message) async {
    await Firebase.initializeApp();
    // 初始化Hive并打开存储盒
    await Hive.initFlutter();
    final notificationBox = await Hive.openBox('notifications');
    // 存储通知数据
    await notificationBox.put(DateTime.now().millisecondsSinceEpoch.toString(), message.data);
  }
  

• 通过端口通信将存储任务移交主进程：

  // 主进程注册消息接收端口
  void main() async {
    WidgetsFlutterBinding.ensureInitialized();
    await Firebase.initializeApp();
    
    final receivePort = ReceivePort();
    IsolateNameServer.registerPortWithName(receivePort.sendPort, 'notification_storage_port');
    
    // 主进程中执行存储操作
    receivePort.listen((notificationData) async {
      final prefs = await SharedPreferences.getInstance();
      final existingNotifications = prefs.getStringList('notifications') ?? [];
      await prefs.setStringList('notifications', [...existingNotifications, notificationData]);
    });
    
    FirebaseMessaging.onBackgroundMessage(firebaseMessagingBackgroundHandler);
    runApp(MyApp());
  }
  
  // 后台隔离区发送消息到主进程
  @pragma('vm:entry-point')
  Future<void> firebaseMessagingBackgroundHandler(RemoteMessage message) async {
    await Firebase.initializeApp();
    final sendPort = IsolateNameServer.lookupPortByName('notification_storage_port');
    sendPort?.send(jsonEncode(message.data));
  }
  

3. 规避Android后台进程限制 #

Android 8.0+对后台进程有严格管控，可能导致存储操作被中断：

• 启动前台服务维持进程存活：

  @pragma('vm:entry-point')
  Future<void> firebaseMessagingBackgroundHandler(RemoteMessage message) async {
    await Firebase.initializeApp();
    
    if (Platform.isAndroid) {
      // 创建后台通知渠道
      const channel = AndroidNotificationChannel(
        'background_process',
        '后台处理通道',
        importance: Importance.low,
      );
      final notificationPlugin = FlutterLocalNotificationsPlugin();
      await notificationPlugin.resolvePlatformSpecificImplementation<AndroidFlutterLocalNotificationsPlugin>()?.createNotificationChannel(channel);
      
      // 启动前台服务
      await notificationPlugin.show(
        1001,
        '后台处理中',
        '正在保存通知',
        NotificationDetails(android: AndroidNotificationDetails(channel.id, channel.name)),
      );
    }
    
    // 执行存储操作
    final notificationBox = await Hive.openBox('notifications');
    await notificationBox.put(DateTime.now().millisecondsSinceEpoch.toString(), message.data);
  }
  

• 引导用户关闭应用的电池优化：在应用设置中找到电池优化选项，将应用设为“不优化”，确保后台进程能正常运行。

4. 添加错误捕获排查问题 #

在后台handler中加入异常捕获，通过Logcat查看具体失败原因：

@pragma('vm:entry-point')
Future<void> firebaseMessagingBackgroundHandler(RemoteMessage message) async {
  try {
    await Firebase.initializeApp();
    final notificationBox = await Hive.openBox('notifications');
    await notificationBox.put(DateTime.now().millisecondsSinceEpoch.toString(), message.data);
    print('通知存储成功');
  } catch (e) {
    print('存储失败详情：$e');
  }
}

内容的提问来源于stack exchange，提问作者nassim Soliman