Flutter Android Alarm Manager应用关闭后失效问题求助

Hey there, let's tackle this alarm issue you're facing—super common with Android's strict background restrictions, especially when comparing real devices vs emulators. Let's break down how to reproduce this reliably and fix it step by step.

• Grab a physical Android device (emulators skip many of Android's background process limits that real devices enforce)
• Set an alarm for 1-2 minutes in the future
• Fully close the app: swipe it away from your recent apps list (this kills the app's process entirely)
• Wait for the alarm time to hit—you'll notice no notification or ringtone plays (whereas it works flawlessly when the app is open)
• For deeper debugging, pull up Android's Logcat and filter logs by your app's package name or keywords like AlarmManager, Notification, or Ringtone to spot errors.

1. Use AlarmManager Methods That Bypass Doze Mode #

Android's Doze mode (introduced in Android 6.0) throttles background operations when the device is idle, and standard alarm methods like setExact() or setRepeating() get delayed indefinitely. You need to use priority methods that bypass Doze:

• For one-time alarms: Use setExactAndAllowWhileIdle() instead of standard alarm calls
• For repeating alarms: Use setAlarmClock() (this is prioritized even in deep Doze)
  Double-check that your Flutter alarm plugin uses these methods under the hood. If you're using a custom platform channel for AlarmManager, update the native Android code to switch to these APIs.

2. Fix Notification Initialization & Channel Setup #

Your NotificationManager.initNotificationManager() is called inside _ringAlarm(), which can fail if the app process is already killed. Instead:

• Initialize flutterLocalNotificationsPlugin when the app first launches (e.g., in your main widget's initState() or a singleton service)
• Pre-create notification channels on app launch (mandatory for Android 8.0+):

  Future<void> createNotificationChannels() async {
    const AndroidNotificationChannel alarmChannel = AndroidNotificationChannel(
      'alarm_channel_id',
      'Alarm Notifications',
      'Notifications for scheduled alarms',
      importance: Importance.max,
      priority: Priority.high,
      sound: RawResourceAndroidNotificationSound('your_alarm_sound'),
    );
    await flutterLocalNotificationsPlugin.resolvePlatformSpecificImplementation<AndroidFlutterLocalNotificationsPlugin>()?.createNotificationChannel(alarmChannel);
  }
  

Call this method once when your app starts, not just when showing a notification.

3. Handle Android 8.0+ Background Service Restrictions #

When the app is closed, your _ringAlarm() runs in a restricted background context. To play the ringtone and show notifications reliably:

• Add these permissions to your AndroidManifest.xml:

  <uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
  <uses-permission android:name="android.permission.WAKE_LOCK" />
  

• When the alarm triggers, start a foreground service before playing the ringtone. This prevents the system from killing your process mid-operation. You can implement this via a platform channel or use a Flutter plugin that supports foreground services.

4. Fix Background Ringtone Playback #

Your FlutterRingtonePlayer.play() call might fail in the background due to audio focus restrictions. Adjust the call to prioritize alarm playback:

FlutterRingtonePlayer.play(
  android: AndroidSounds.alarm,
  ios: IosSounds.glass,
  looping: true,
  volume: 1,
  asAlarm: true, // Critical for background playback on Android
);

If you need to bypass Do Not Disturb mode, add the ACCESS_NOTIFICATION_POLICY permission to your manifest.

5. Validate Alarm Receiver Registration #

Double-check your AndroidManifest.xml to ensure your alarm receiver is properly registered and exported:

<receiver
    android:name=".AlarmReceiver"
    android:exported="true"
    android:enabled="true">
    <intent-filter>
        <action android:name="android.intent.action.BOOT_COMPLETED" />
        <action android:name="android.intent.action.TIME_SET" />
    </intent-filter>
</receiver>

This ensures the receiver can be triggered even when the app isn't running.

Start with updating the AlarmManager method, then fix the notification initialization flow. Testing on a real device is non-negotiable here—emulators don't replicate all of Android's background behavior constraints.

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