Android应用关闭后AlarmManager无法触发BroadcastReceiver求助

问题诊断与修复步骤 #

1. 修正PendingIntent的创建上下文 #

ScheduleNextAlarm方法中使用Platform.CurrentActivity创建Intent和PendingIntent，当应用后台关闭后，该Activity实例可能已销毁，导致PendingIntent无法正常触发。应改用OnReceive传入的context来创建：

private void ScheduleNextAlarm(Context context)
{
    var alarmIntent = new Intent(context, typeof(MyAlarmService));
    alarmIntent.SetAction("com.companyname.appName.START_ALARM");
    
    // 适配Android 12+，添加Mutable标志
    var flags = PendingIntentFlags.UpdateCurrent;
    if (Build.VERSION.SdkInt >= BuildVersionCodes.S)
    {
        flags |= PendingIntentFlags.Mutable;
    }
    var pendingIntent = PendingIntent.GetBroadcast(context, 0, alarmIntent, flags);

    var alarmManager = (AlarmManager)context.GetSystemService(Context.AlarmService);

    // 修正触发时间计算错误
    long triggerTime = SystemClock.ElapsedRealtime() + 6 * 1000;
    alarmManager.SetExactAndAllowWhileIdle(AlarmType.ElapsedRealtimeWakeup, triggerTime, pendingIntent);
}

2. 修复AlarmManager触发时间计算错误 #

原代码重复累加SystemClock.ElapsedRealtime()，导致触发时间远超预期，需直接使用计算好的triggerTime。同时为突破Doze模式限制，建议用SetExactAndAllowWhileIdle替代SetExact。

3. 解决Async void导致的生命周期问题 #

BroadcastReceiver的OnReceive执行完毕后，进程可能被系统回收，而async void的ExecuteStuff异步操作未完成就会中断。可改为以下方案：

public override async void OnReceive(Context? context, Intent? intent)
{
    PowerManager pm = (PowerManager)context.GetSystemService(Context.PowerService);
    var wakeLock = pm.NewWakeLock(WakeLockFlags.Partial, "YourWakeLockTag");
    wakeLock.Acquire(10*60*1000); // 设置超时时间，避免死锁

    try
    {
        await ExecuteStuff(context); // 改为async Task方法
        ScheduleNextAlarm(context);
    }
    finally
    {
        if (wakeLock.IsHeld)
        {
            wakeLock.Release();
        }
    }
}

// 改为async Task而非async void
private async Task ExecuteStuff(Context context)
{
    var manageNotifications = new ManageNotifications();
    var notificationFromDB = await manageNotifications.CheckNotificationForSending();

    if (!string.IsNullOrWhiteSpace(notificationFromDB.ExecutionTime))
    {
        // 使用传入的context而非Platform.CurrentActivity
        var notificationToSend = new NotificationCompat.Builder(context, "1002")
          .SetSmallIcon(Resource.Drawable.logo)
          .SetContentTitle(notificationFromDB.Title)
          .SetContentText(notificationFromDB.Message)
          .SetPriority(NotificationCompat.PriorityHigh)
          .SetGroup("example_group")
          .SetSound(RingtoneManager.GetDefaultUri(RingtoneType.Notification))
          .Build();

        var notificationManager = NotificationManagerCompat.From(context);
        notificationManager.Notify(2, notificationToSend);
    }
}

4. 移除Manifest中的remote进程配置 #

android:process=":remote"会让BroadcastReceiver在独立进程运行，系统资源紧张时会优先杀死这类非主进程，导致后台无法触发。修改Manifest配置：

<receiver android:name=".MyAlarmService"
          android:exported="true">
    <intent-filter>
        <action android:name="com.companyname.appName.START_ALARM"/>
    </intent-filter>
</receiver>

5. 适配Android后台限制 #

• 电池优化白名单：引导用户将应用加入电池优化白名单，避免Doze模式阻止闹钟触发：

if (Build.VERSION.SdkInt >= BuildVersionCodes.M)
{
    PowerManager pm = (PowerManager)context.GetSystemService(Context.PowerService);
    if (!pm.IsIgnoringBatteryOptimizations(context.PackageName))
    {
        Intent intent = new Intent(Settings.ActionRequestIgnoreBatteryOptimizations);
        intent.SetData(Uri.Parse("package:" + context.PackageName));
        intent.AddFlags(ActivityFlags.NewTask);
        context.StartActivity(intent);
    }
}

• 添加权限：在Manifest中声明必要权限：

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

6. 确保初始闹钟的正确触发 #

初始调用闹钟时，同样使用SetExactAndAllowWhileIdle，并通过Application Context或当前Activity的Context创建PendingIntent，避免上下文失效。

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