Fix booster notification background trigger (EXPOSUREAPP-11804) #4838

LukasLechnerDev · 2022-02-15T11:23:06Z

This PR fixes the issue that the booster notifications are not triggered by our background worker.

Because of a copy-paste mistake of mine (in WorkerBinder.kt), the background worker did actually never run...

How to test:

Fresh install
Start app
Switch to WRU and set "fake correct device time" in Remote Config Data Test Menu (Not sure if this switch is really necessary to set
Close app
Set device time to 2022-02-10 12:30
Open App
Force ccl config update (config from WRU and INT are different)
Scan certificate from the ticket
See that booster notification shows up
Close app and click on notification
Close app
Set device time 24h into the future (2022-02-11 12:30)
Without opening the app, the worker should start its work and the booster notificaiton should appear

LukasLechnerDev · 2022-02-15T11:24:11Z

...c/main/java/de/rki/coronawarnapp/ccl/configuration/update/CCLConfigurationUpdateScheduler.kt

        return PeriodicWorkRequestBuilder<CCLConfigurationUpdateWorker>(
            repeatInterval = 24,
            repeatIntervalTimeUnit = TimeUnit.HOURS
-        ).setConstraints(constraints).build()
+        ).setInitialDelay(


Not related to the bug, but I added a 1 minute delay for the worker so that the app and the worker won't both update the config after app start at the same time.

LukasLechnerDev · 2022-02-15T11:30:51Z

...c/main/java/de/rki/coronawarnapp/ccl/configuration/update/CCLConfigurationUpdateScheduler.kt

@@ -48,14 +47,13 @@ class CCLConfigurationUpdateScheduler @Inject constructor(
    }

    private fun buildWorkRequest(): PeriodicWorkRequest {
-        val constraints = Constraints.Builder()


We shouldn't only run the worker when we have network connection, since the dccwallet recalculation should run daily even if we can't get the config from the network.