后台Service仍有未完成任务时onDestroy被调用问题

应用处于后台时，Service中运行CountDownTimer。在onFinish()方法中本应判断启动另一个计时器或发送通知，但启动第二个计时器的瞬间，onDestroy方法被调用。

onStartCommand 实现 #

override fun onStartCommand(intent: Intent?, flags: Int, startId: Int): Int {
    startTimer()
    return START_STICKY
}

startTimer 实现 #

private fun startTimer() {
    val context = this
    Timber.tag(TAG).d("startTimer: called with time left " + timeLeftInMillis / 1000)
    Timber.tag(TAG).d("startTimer: called timerType is " + timerType)

    // get values from datastore
    timer = object : CountDownTimer(timeLeftInMillis, 1000) {
        override fun onTick(millisUntilFinished: Long) {
            timeLeftInMillis = millisUntilFinished
            // Update notification text with remaining time
            notificationBuilder.setContentText("Time remaining: ${millisUntilFinished / 1000} seconds")
            notificationManager.notify(NOTIFICATION_ID, notificationBuilder.build())
        }

        override fun onFinish() {
            timerState = TimerState.STOPPED
            if (timerType == TimerType.LONGBREAK || timerType == TimerType.SHORTBREAK) {
                //save timer values to dataStore
                scope.launch {
                    currentPom++
                    timerType = TimerType.FOCUS
                    timerState = TimerState.STOPPED
                    dataStoreManager.saveRunningParams(
                        timeLeftInMillis,
                        timerType.ordinal,
                        timerState.ordinal,
                        appVisibility.ordinal,
                        currentPom
                    )
                    //send notification
                    showTimerCompleteNotification(context)
                }
            } else if (timerType == TimerType.FOCUS) {
                //start next timer
                nextTimer()
                loadPomValues()
                startTimer()
            }
        }
    }

    timer.start()
}

2024-01-06 10:25:17.631 15069-15069 TimerService com.example.taskrabbit   D  TimerService nextTimer: Called
2024-01-06 10:25:17.632 15069-15069 TimerService com.example.taskrabbit   D  TimerService nextTimer: current timer type is SHORTBREAK
2024-01-06 10:25:17.632 15069-15069 TimerService com.example.taskrabbit   D  startTimer: called with time left 60
2024-01-06 10:25:17.633 15069-15069 TimerService com.example.taskrabbit   D  startTimer: called timerType is SHORTBREAK
2024-01-06 10:25:17.634 15069-15069 TimerService com.example.taskrabbit   D  onDestroy: called
2024-01-06 10:25:17.636 15069-15099 TimerService com.example.taskrabbit   D  onDestroy: Time left in millis is: 60

核心原因 #

1. 后台Service回收限制：Android O及以上版本对后台Service管控严格，当应用处于后台且Service未标记为前台服务时，系统会认为它无持续运行的必要，在第一个计时器结束、新计时器启动的间隙触发回收。
2. 内部调用的局限性：在onFinish中直接调用startTimer只是创建新计时器，但未向系统明确声明Service需要继续运行，系统仍会判定Service可销毁。

解决步骤 #

1. 将Service设为前台服务
   在startTimer启动计时器前，调用startForeground(NOTIFICATION_ID, notificationBuilder.build())，让Service处于前台状态，规避系统的后台回收逻辑。注意Android O及以上需提前创建通知渠道。

2. 通过启动Service触发计时器重启
   把onFinish中直接调用startTimer的逻辑，替换为调用startForegroundService(Intent(this, TimerService::class.java))，让系统重新触发onStartCommand，明确告知系统Service需要持续运行。同时在onStartCommand中判断是否已有活跃计时器，避免重复创建。

3. 清理计时器资源
   在onDestroy方法中添加timer?.cancel()，确保旧计时器被正确终止，避免内存泄漏和后台无效操作。

4. 优化状态同步
   在启动新计时器前，确保timerType、timeLeftInMillis等状态已写入DataStore，避免Service重启后状态丢失。

内容的提问来源于stack exchange，提问作者Blaise Lukwayi N