AlarmManager setExact() 失效问题：每日/每周定时任务异常求助

Hey there, let's dig into why your AlarmManager setExact() isn't working as expected for those daily/weekly cache-clearing tasks. I've dealt with similar headaches before, so here are the most common culprits and actionable fixes:

1. Doze Mode & Battery Optimization Throttling #

Starting from Android 6.0 (API 23), Doze Mode and App Standby restrict background operations—including standard setExact() alarms—to save battery. If your app isn't active, the alarm might get delayed or never fire.

• Quick Fix: Use setExactAndAllowWhileIdle() instead for critical tasks like your cache clearing. This method bypasses Doze restrictions, but use it sparingly (only for tasks that absolutely need to run on time).
• Backup Option: You can prompt users to exclude your app from battery optimization via the ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS intent, but this should be a last resort as it can erode user trust.

2. Duplicate PendingIntent Overwriting Alarms #

If your daily and weekly alarms use the same requestCode or identical Intent configurations, the second alarm will overwrite the first one.

• Check & Fix: Ensure unique requestCode values (e.g., 100 for daily, 200 for weekly) and add distinct extras to each Intent to avoid PendingIntent collisions. Here's how to adjust your code:

// Daily alarm setup
val dailyIntent = Intent(context, ClearDataReceiver::class.java).apply {
    putExtra(ClearDataReceiver.DATA_TYPE_EXTRA, dataType)
    putExtra("ALARM_TYPE", "DAILY")
}
val dailyPendingIntent = PendingIntent.getBroadcast(
    context,
    100, // Unique request code
    dailyIntent,
    PendingIntent.FLAG_UPDATE_CURRENT or PendingIntent.FLAG_IMMUTABLE // Use FLAG_IMMUTABLE for API 31+
)

// Weekly alarm setup
val weeklyIntent = Intent(context, ClearDataReceiver::class.java).apply {
    putExtra(ClearDataReceiver.DATA_TYPE_EXTRA, dataType)
    putExtra("ALARM_TYPE", "WEEKLY")
}
val weeklyPendingIntent = PendingIntent.getBroadcast(
    context,
    200, // Different request code
    weeklyIntent,
    PendingIntent.FLAG_UPDATE_CURRENT or PendingIntent.FLAG_IMMUTABLE
)

3. Incorrect Alarm Time Calculation #

If the current time is already past 23:59, your calendar setup will trigger the alarm immediately instead of the next day/week.

• Fix: Add a check to shift the target time forward if it's in the past:

val calendar = Calendar.getInstance().apply {
    timeInMillis = System.currentTimeMillis()
    set(Calendar.HOUR_OF_DAY, 23)
    set(Calendar.MINUTE, 59)
    set(Calendar.SECOND, 0)
    set(Calendar.MILLISECOND, 0)

    // For daily alarm: if current time is past 23:59, set to next day
    if (before(Calendar.getInstance())) {
        add(Calendar.DAY_OF_MONTH, 1)
    }

    // For weekly alarm: set to the target weekday, then shift a week if needed
    // Example: Set to every Sunday 23:59
    // set(Calendar.DAY_OF_WEEK, Calendar.SUNDAY)
    // if (before(Calendar.getInstance())) {
    //     add(Calendar.WEEK_OF_YEAR, 1)
    // }
}

4. Missing or Incorrect Receiver Registration #

Your ClearDataReceiver won't receive the alarm broadcast if it's not properly registered.

• Manifest Registration Example:

<receiver
    android:name=".ClearDataReceiver"
    android:exported="false">
    <!-- Explicit intents don't require filters, but add them if needed -->
</receiver>

If you're using dynamic registration, make sure you register it when the app starts and unregister it only when necessary.

5. Emulator Limitations #

Emulators often have inconsistent AlarmManager behavior, especially with Doze Mode. Test your alarms on a physical Android device to rule out emulator-specific issues.

6. Aggressive OEM App Killing #

Many manufacturers (Xiaomi, Huawei, Samsung) have strict background policies that cancel alarms when the app is swiped from recent apps.

• Fix: Guide users to enable "Auto-Start" or "Background Activity" permissions for your app in the device settings. You can add in-app instructions tailored to common OEMs to make this easier for users.

After applying these fixes, your alarms should fire reliably. If you hit a specific snag with any of these steps, feel free to share more details!

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