咨询Flutter应用关闭时执行用户与OneSignal PlayerID解绑函数的方案

Hey there! I totally get the frustration—WillPopScope only covers back button presses, which is way too narrow for your use case. You need to catch every possible way the app could close (whether the user swipes it away, the system kills it to free memory, or they restart their device) to unbind the PlayerID when "Keep me logged in" is turned off. Let’s break down a comprehensive solution step by step:

1. Use WidgetsBindingObserver for Core App Lifecycle Events #

This lets you listen to general app state changes, like when the app moves to the background or gets detached from the engine. Here’s how to set it up:

First, add the observer to your root widget:

class MyApp extends StatefulWidget {
  @override
  _MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> with WidgetsBindingObserver {
  @override
  void initState() {
    super.initState();
    WidgetsBinding.instance.addObserver(this);
  }

  @override
  void dispose() {
    WidgetsBinding.instance.removeObserver(this);
    super.dispose();
  }

Then override the lifecycle method to trigger unbinding when needed:

@override
  void didChangeAppLifecycleState(AppLifecycleState state) {
    super.didChangeAppLifecycleState(state);
    
    // Fetch the user's "keep logged in" preference from local storage
    bool keepLoggedIn = await _getKeepLoggedInStatus();
    
    if (!keepLoggedIn) {
      switch (state) {
        case AppLifecycleState.detached:
          // App is being fully detached from the engine (likely terminated)
          _unbindPlayerID();
          break;
        case AppLifecycleState.inactive:
          // App is inactive (e.g., incoming call, home button press on iOS)
          // This is a precursor to termination on iOS, so we trigger unbinding here
          _unbindPlayerID();
          break;
        default:
          break;
      }
    }
  }

  Future<bool> _getKeepLoggedInStatus() async {
    final prefs = await SharedPreferences.getInstance();
    return prefs.getBool('keep_logged_in') ?? false;
  }

  void _unbindPlayerID() {
    // Call your OneSignal unbinding logic here
    OneSignal.removeExternalUserId(); // Example OneSignal method
  }

2. Add Native Platform Listeners (Critical for Edge Cases) #

Flutter’s lifecycle doesn’t cover every termination scenario (like when the system kills the app to free up resources). You’ll need native code to catch these events and notify Flutter:

For Android: #

In your MainActivity.kt (or Java), listen for onTaskRemoved and onDestroy, then send a signal to Flutter via a MethodChannel:

class MainActivity : FlutterActivity() {
    private lateinit var channel: MethodChannel

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        channel = MethodChannel(flutterEngine?.dartExecutor?.binaryMessenger, "app_termination")
    }

    override fun onTaskRemoved(rootIntent: Intent?) {
        super.onTaskRemoved(rootIntent)
        // Triggered when user swipes the app away from recent apps
        channel.invokeMethod("onAppTerminated", null)
    }

    override fun onDestroy() {
        super.onDestroy()
        // Triggered when the app is fully destroyed
        channel.invokeMethod("onAppTerminated", null)
    }
}

For iOS: #

In your AppDelegate.swift, use applicationWillTerminate to notify Flutter:

import UIKit
import Flutter

@UIApplicationMain
@objc class AppDelegate: FlutterAppDelegate {
    override func application(
        _ application: UIApplication,
        didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
    ) -> Bool {
        let controller = window?.rootViewController as! FlutterViewController
        let channel = FlutterMethodChannel(name: "app_termination", binaryMessenger: controller.binaryMessenger)
        GeneratedPluginRegistrant.register(with: self)
        return super.application(application, didFinishLaunchingWithOptions: launchOptions)
    }

    override func applicationWillTerminate(_ application: UIApplication) {
        // Triggered when the app is about to terminate
        let controller = window?.rootViewController as! FlutterViewController
        let channel = FlutterMethodChannel(name: "app_termination", binaryMessenger: controller.binaryMessenger)
        channel.invokeMethod("onAppTerminated", arguments: nil)
    }
}

Flutter Side for Native Channel: #

Listen to the channel in your root widget to trigger unbinding:

@override
void initState() {
  super.initState();
  WidgetsBinding.instance.addObserver(this);
  
  // Set up MethodChannel to listen for native termination signals
  const MethodChannel channel = MethodChannel('app_termination');
  channel.setMethodCallHandler((MethodCall call) async {
    if (call.method == 'onAppTerminated') {
      bool keepLoggedIn = await _getKeepLoggedInStatus();
      if (!keepLoggedIn) {
        _unbindPlayerID();
      }
    }
  });
}

3. Keep WillPopScope for Back Button Presses #

Don’t forget to retain WillPopScope for Android back button presses—it’s still a common way users exit the app:

WillPopScope(
  onWillPop: () async {
    bool keepLoggedIn = await _getKeepLoggedInStatus();
    if (!keepLoggedIn) {
      _unbindPlayerID();
    }
    return true; // Allow back navigation
  },
  child: // Your main app content
)

Key Tips to Avoid Issues #

• Keep Unbinding Lightweight: System termination events have strict time limits—make your _unbindPlayerID method as fast as possible (avoid heavy async operations if you can).
• Sync Preferences Immediately: Save the "keep logged in" status to SharedPreferences right when the user toggles it, so your listeners always have the correct value.
• Test Edge Cases: Test scenarios like swiping the app away, restarting the device, and letting the system kill the app in the background to ensure unbinding works every time.

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