Flutter中Work Manager结合本地通知的页面跳转问题

核心思路：后台任务仅负责触发通知，导航逻辑通过全局导航键+前台通知点击回调实现——因为后台任务运行在隔离环境中，无法直接获取Context。

步骤1：定义全局导航键 #

在main.dart顶部定义全局NavigatorState键，用于无Context场景下控制导航：

import 'package:flutter/material.dart';

// 全局导航键，必须放在MyApp外部
final GlobalKey<NavigatorState> navigatorKey = GlobalKey<NavigatorState>();

步骤2：前台初始化通知插件并配置点击回调 #

将通知插件的初始化移到MyApp生命周期中，同时设置onSelectNotification回调处理导航逻辑：

class _MyAppState extends State<MyApp> {
  late FlutterLocalNotificationsPlugin _notificationsPlugin;

  @override
  void initState() {
    super.initState();
    workmanagerFunction();
    _initNotifications(); // 初始化通知插件
  }

  // 初始化通知插件并配置点击回调
  void _initNotifications() async {
    _notificationsPlugin = FlutterLocalNotificationsPlugin();
    const androidInit = AndroidInitializationSettings('@mipmap/ic_launcher');
    const iosInit = IOSInitializationSettings();
    const settings = InitializationSettings(android: androidInit, iOS: iosInit);

    // 通知点击后的导航逻辑
    await _notificationsPlugin.initialize(settings, onSelectNotification: (payload) async {
      if (payload != null) {
        // 根据payload跳转到指定页面，示例为SecondPage
        navigatorKey.currentState?.push(MaterialPageRoute(
          builder: (context) => SecondPage(),
        ));
      }
    });
  }

  // ...原有的workmanagerFunction等代码
}

步骤3：修改后台任务的通知触发逻辑 #

后台任务中无需重复配置通知回调，仅需创建插件实例并触发通知，同时传递标识性payload：

void callbackDispatcher() async {
  Workmanager().executeTask((dynamic task, dynamic inputData) async {
    print('Background Services are Working!');

    // ...你的业务逻辑代码

    if (count > await data()['count']) {
      FlutterLocalNotificationsPlugin flip = FlutterLocalNotificationsPlugin();
      var android = const AndroidInitializationSettings('@mipmap/ic_launcher');
      var IOS = const IOSInitializationSettings();
      var settings = InitializationSettings(android: android, iOS: IOS);
      await flip.initialize(settings); // 后台初始化仅用于触发通知

      await _showNotificationWithDefaultSound(flip);

      // ...你的Firestore更新代码
      return Future.value(true);
    } else {
      return true;
    }
  });
}

// 修改通知方法，传递明确的页面标识payload
Future _showNotificationWithDefaultSound(FlutterLocalNotificationsPlugin flip) async {
  var androidPlatformChannelSpecifics = const AndroidNotificationDetails(
      'your channel id',
      'your channel name',
      importance: Importance.max,
      priority: Priority.high
  );
  var iOSPlatformChannelSpecifics = const IOSNotificationDetails();
  var platformChannelSpecifics = NotificationDetails(
      android: androidPlatformChannelSpecifics,
      iOS: iOSPlatformChannelSpecifics
  );
  await flip.show(
      0,
      'end of the calls',
      'you should click',
      platformChannelSpecifics,
      payload: 'second_page', // 传递页面标识，用于回调判断跳转目标
  );
}

步骤4：处理应用冷启动时的通知点击 #

如果应用完全关闭，点击通知启动应用时，需要在MaterialApp中处理初始路由：

@override
Widget build(BuildContext context) {
  return MaterialApp(
    navigatorKey: navigatorKey,
    debugShowCheckedModeBanner: false,
    title: 'Dentapros Call Logs',
    theme: ThemeData(
        visualDensity: VisualDensity.adaptivePlatformDensity,
        primaryColor: Colors.deepPurple,
        appBarTheme: AppBarTheme(color: Colors.indigo.shade900)),
    // 处理冷启动时的通知payload
    onGenerateRoute: (settings) {
      final payload = settings.arguments as String?;
      if (payload == 'second_page') {
        return MaterialPageRoute(builder: (context) => SecondPage());
      }
      return MaterialPageRoute(builder: (context) => FirstPage());
    },
  );
}

关键注意点 #

• 后台任务运行在独立Isolate中，无法访问前台Context或全局状态，导航逻辑必须放在前台处理。
• 全局navigatorKey是实现无Context导航的核心，必须确保MaterialApp正确使用该键。
• 通知的payload可根据业务需求自定义，用于区分不同的跳转目标。

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