Background update does not work, CWA 1.9.1 and “prioritized background activity”

[speedy-1702]

Version 1.1.1 is installed since last week and “prioritized background activity” is set to on. Today I clicked on my risk status and saw that the last update was two days ago ("vorgestern").

Is this how it is supposed to be?

Some seconds later, the update was performed.

Device is a Huawei P30 lite running with Android 10.0.0

---

Internal Tracking ID: EXPOSUREAPP-1922

[gusowski1]

I could confirm the issue.

Honor 10 (COL-L29) Android 10 EMUI 10.0.0 Build 10.0.0.177(C432E3R1P4patch01) CWA 1.1.1 ENF 15202902003

no check 2020/07/24. prioritized background activity enabled from within the app

[benjussuf]

Same issue on bq Aquaris X, Android 8.1.0. Automatic updates worked in Version 1.0.5.

[NKarolak]

Same issue on a Samsung Galaxy S10e on Android 10. I reboot the phone every day. I am using the latest app version, and excluded it from the phone's energy optimization. The last time I've used the app was over 24 hours ago (July 26, 2020 14:49 - now it's July 27, 17:15)

I've checked the entries under Settings --> Google --> COVID-19 Notifications. They don't get updated until I open the app again.

[swe0815]

Same issue on Xiaomi Mi9 Android 10 with the latest patches "Priorisierte Hintergrundaktivität" is turned on

Same problem "I've checked the entries under Settings --> Google --> COVID-19 Notifications. They don't get updated until I open the app again."

[mbw83]

I also have the issue on a Xiaomi Mi 9 Lite. This is also reported in #756, but I think we can't expect the developers to take care of this. For me open source is not defined as "putting the code somewhere and don't care afterwards", open source means for me also taking the advantages and especially using for example this issue tracker. But I don't have the impression, that the developers are using this. If they would, they should communicate more often!

And to be honest: They are getting a hell of money from "us" and the "only" thing the app has to do is downloading keys of infected persons every roughly 24 hours and showing a notification if the user is infected. But the app is not able to reliable do this.

[MikeMcC399]

Is there any way in the production version of CWA (currently Version 1.1.1) to see when the next risk evaluation is scheduled? I only know how to look via Settings > Google > COVID-19 exposure notifications > Exposure checks to see what requests have been previously made.

[SebastianWolf-SAP]

@mbw83 We are taking this issue (and the others of course as well) seriously. We are continuously checking if we can reproduce the issue with the devices people have mentioned here. So please keep on posting the devices which still face the issues. We are taking them into account in further test efforts.

@MikeMcC399 The latest update is also shown on the home screen of the app. The next automated evaluation is scheduled for 24 hours later. It depends on OS scheduling and other aspects when it will actually happen. Usually it's 24 hours plus a little bit more. Only if the next update happens later than 24+4 hours after the last update, the scheduling hasn't worked properly and we recommend opening the app manually once again.

[thomasaugsten]

can you please double check in OS settings if the app is excluded from the phone's energy optimization/ akkuoptimierung Also try to restart the phone and start the app once and check after ~28h if there is an entry in COVID-19 Notifications. Please check this page https://dontkillmyapp.com/ for a working solution for your device.

[MikeMcC399]

@SebastianWolf-SAP

The latest update is also shown on the home screen of the app. The next automated evaluation is scheduled for 24 hours later. It depends on OS scheduling and other aspects when it will actually happen. Usually it's 24 hours plus a little bit more. Only if the next update happens later than 24+4 hours after the last update, the scheduling hasn't worked properly and we recommend opening the app manually once again.

Thank you for describing the expected interval of 24+4. Today my Samsung Galaxy A50 / Android 10 device did an automatic risk update at 19:35 following on from a previous automatic risk update the previous day at 7:25. This is an interval of 24:00+12:10. I have not opened CWA during this time, so the automatic risk update is delayed more than 8 hours (12:10 - 4:00) compared to what was expected.

[thomasaugsten]

@MikeMcC399 Was there any special conditions like heavy load, low battery or poor network connection?

[speedy-1702]

@thomasaugsten

can you please double check in OS settings if the app is excluded from the phone's energy optimization/ akkuoptimierung Also try to restart the phone and start the app once and check after ~28h if there is an entry in COVID-19 Notifications. Please check this page https://dontkillmyapp.com/ for a working solution for your device.

Double check is done. Corona warn app is excluded from battery optimization

Restart is done. I will report here after ~28 hours.

[MikeMcC399]

@thomasaugsten

Was there any special conditions like heavy load, low battery or poor network connection?

No special conditions were occurring. I am checking against https://dontkillmyapp.com/. Although my model is not specifically referenced I think I can still infer what settings might help and I will try them out.

[w-flo]

I wasn't involved in Android development in recent years, so take this with a grain of salt, but someone mentioned that foreground services should be used instead of background services, because they are less likely to be killed. They received no response to that comment.

Does corona-warn-app already use a foreground service for risk updates? Since foreground services must show a notification while they are active, and I haven't noticed any "update in progress" notifications from CWA, I assume it is a background service right now? If so, shouldn't the implementation be changed to use a foreground service instead?

Also regarding the scheduled update time, I can't confirm that the next update will take place 24 hours after the previous update. It appears like my phone used to schedule automatic updates at 6pm, but I've since switched to manually opening the app at ~6am instead, and 7am or 8am on weekends. The app never scheduled an automatic update at ~6am on weekends, it was always triggered by my opening the app a few hours later. I guess automatic updates are still scheduled for 6pm, so that would be 36 hours after my last manually triggered update.

[matherm]

@w-flo I would not recommend a foreground service as this causes the app to "run" all the time. More or less an endless loop. There are ways to mitigate, but using scheduled tasks AlarmManager and WorkManager is imho the correct pattern. Unfortunately, it seems that in the work scheduler API is not using AlarmManger but seems to choose TaskScheduler which is more energy efficient (bulk updates), but obviously ia not reliable on some devices/OS. If changing something I would rather propose to change to AlarmManger with setExactAndAllowWhileIdle() instead. Of course, this would impact battery life.

As already reported in #637 there is a general android problem with background processing on several devices. https://issuetracker.google.com/issues/122098785

Another interesting thing appears in my Settings --> Google --> COVID-19 Notifications. It seems that the keys are checked multiple times with the same timestamp. However, it only dates back 4 days. I guess that's because the list only shows the latest 100 entries. Anyway, it seems as it is updating too often.

Nokia 7 plus Android 10 (latest) Corona-app 1.1.1

[vaubaehn]

@matherm

As already reported in #637 there is a general android problem with background processing on several devices. https://issuetracker.google.com/issues/122098785

Very interesting link, but very frustrating to read...

Comment no. 91 in that linked issue thread has a nice idea... Maybe it is possible to ask Google, to implement a scheduled task to the ENF, that triggers the registered exposure notification app (for us: CWA) to run every couple of hours per day? Is something like this technically possible? (Underlaying logic: GPS/GMS/ENF doesn't get killed by battery optimisation. GPS/ENF schedules a task to wake up (run) EN-App. EN-App is awake again, and shows 'the finger' to device manufacturer's battery optimisation/background process killing.)

[MikeMcC399]

@vaubaehn

Maybe it is possible to ask Google, to implement a scheduled task to the ENF, that triggers the registered exposure notification app (for us: CWA) to run every couple of hours per day? Is something like this technically possible?

I read about the following improvement in the ENF: "App force-stop improvements: if an app has been force-stopped in the background, the Exposure Notifications service will wake it up again automatically." in the Exposure Notifications release notes . Is this functionality doing what it is described to do, and if yes, why isn't that enough to solve the issue? Does anybody know?

[vaubaehn]

@MikeMcC399 Thanks very much for that hint. Actually, I knew the release notes but overlooked it there! For me it looks like the way to go. Obviously it still seems to be buggy or not fully functional, would need a closer look together from google and our devs here, imho.

[thomasaugsten]

@MikeMcC399 thanks for pointing out this new feature. We are working day and night together with Google to improve the app. This new feature will be adopted soon by our app and should increase the stability of the background task.

[daimpi]

Here is an overview of some Android devices from friends/family. “Prioritized Background Activity” (PBA) was activated manually on all the devices on the 24.07. and I followed the Button in CWA to the device settings to check that the App is actually exempt from “Energy Saving”. I checked the logs for those phones on the 24th (the day of activating PBA) and on 28.07. to see whether days were missing before/after enabling PBA.

All Phones were running CWA version 1.1.1, and ENF version 15202902003.

The Phones checked were:

• 2x Samsung Galaxy S8 (Android 9): Both had lots of entries missing before the 24th, and were working perfectly afterwards even though the users didn’t regularly open the app manually.

• LG G5 (Android 8): This was the only phone where the checks were performed every day even before the 24th. Unsurprisingly everything also worked fine after the 24th.

• Samsung Galaxy S10e (Android 10): App was not working before the 24th (no checks within the last 14 days as the user hadn’t manually opened the app). Afterwards it was working perfectly even though the user didn’t regularly open the app manually.

• Xiaomi Redmi 5 Plus (Android 8.1) and Xiaomi Redmi Note 7 (Android 9): Before the 24th: the App was not working properly, only when manually opened checks were performed. Unfortunately, this didn’t change after the 24th even though PBA was enabled on both devices (one check was automatically performed on the 25th, but nothing afterwards).

Screenshot of the Redmi Note 7 Energy settings:

---

So in summary: On the Samsung devices setting PBA to “on” fixed the Problem. On the LG G5 there was no problem to start with, and CWA continued to work reliably after setting PBA.

Unfortunately for both Xiaomi devices activating PBA didn’t help.

[vaubaehn]

@daimpi very nice and useful research! That information might be very useful to the public also.

[NKarolak]

As written earlier, my Samsung Galaxy s10e was NOT fixed by activating PBA. However, I've updated another setting (disabled it), and I need to wait for a new test result.

Result: https://github.com/corona-warn-app/cwa-app-android/issues/933#issuecomment-667567909

[speedy-1702]

@thomasaugsten

can you please double check in OS settings if the app is excluded from the phone's energy optimization/ akkuoptimierung Also try to restart the phone and start the app once and check after ~28h if there is an entry in COVID-19 Notifications. Please check this page https://dontkillmyapp.com/ for a working solution for your device.

After reboot and waiting for ~28 hours still no improvement. When starting CWA the update started immediately. ("Aktualisiert: Heute, 7:46")

More details can be provided on request

[MikeMcC399]

@thomasaugsten @speedy-1702

After reboot and waiting for ~28 hours still no improvement. When starting CWA the update started immediately. ("Aktualisiert: Heute, 7:46")

I have also seen updates taking longer than 28 hours and I am beginning to suspect there are multiple root causes for the issue of risk update not running reliably without user interaction. I have been trying to check by using a USB cable and debugging with Android Debug Bridge (adb). I am though a complete newby at this!

I have one Samsung Galaxy Android 8 device that updated yesterday at 06:32 and I am puzzled that adb shell dumpsys jobscheduler is showing an entry where the job seems to want to run for another 23h21m. It is currently 08:35, so I would expect it to run the next risk update within the next 2 hours (maximum of 24 +4 hours after the previous run). I will have to wait until 10:32 this morning to check whether the Google COVID-19 UI is telling me that it ran or not.

Here is a relevant portion of the output of adb shell dumpsys jobscheduler:

JOB #u0a172/0: 9365b07 de.rki.coronawarnapp/androidx.work.impl.background.systemjob.SystemJobService u0a172 tag=job/de.rki.coronawarnapp/androidx.work.impl.background.systemjob.SystemJobService Source: uid=u0a172 user=0 pkg=de.rki.coronawarnapp JobInfo: Service: de.rki.coronawarnapp/androidx.work.impl.background.systemjob.SystemJobService Requires: charging=false batteryNotLow=true deviceIdle=false Extras: mParcelledData.dataSize=180 Minimum latency: +23h59m59s972ms Backoff: policy=0 initial=+1m0s0ms Has early constraint Required constraints: BATTERY_NOT_LOW TIMING_DELAY Satisfied constraints: CHARGING BATTERY_NOT_LOW APP_NOT_IDLE DEVICE_NOT_DOZING Unsatisfied constraints: TIMING_DELAY Doze whitelisted: true Tracking: BATTERY TIME Enqueue time: -38m59s343ms Run time: earliest=+23h21m0s628ms, latest=none Ready: false (job=false user=true !pending=true !active=true !backingup=true comp=true)

Update

At 10:39 today the Google ENF UI is showing that a risk update was carried out at 07:55 which is 3 minutes after I first opened the UI at 07:52 today. So currently the automatic risk update is working for me on this device. I guess that the jobscheduler output above was pulled a few minutes after the risk update took place. I didn't check the Google ENF UI again until 10:39.

CWA > Settings > Prioritized Background Activity was already set to "On". This is confirmed by jobscheduler showing "Doze whitelisted: true" and (Android) Settings > Apps > Corona-Warn > Battery shows Optimise battery usage as "Not optimised" so I should have ruled out that CWA is killed by Samsung's battery saving.

I will keep monitoring the risk updates and see if there is anything strange happens.

[mbw83]

can you please double check in OS settings if the app is excluded from the phone's energy optimization/ akkuoptimierung Also try to restart the phone and start the app once and check after ~28h if there is an entry in COVID-19 Notifications. Please check this page https://dontkillmyapp.com/ for a working solution for your device.

It also does not work on my Mi 9 Lite. The battery saving settings are off since a few weeks (I switched them of the first time it was recommended by a developer). Yesterday morning I double checked it, rebooted my device, started the app (updated 6:53) and waited until now (so ~30 hours). The update takes place immediately when starting the app (12:42) and not on its own.

[MikeMcC399]

The current date / time is Jul 30, 2020 15:00 and I am looking at another device (a Samsung Galaxy A50 running Android 10).

Settings > Google > COVID-19 exposure notifications shows "Last checked for potential exposure on yesterday at 10:54" 24 + 4 hours after 10:54 is 14:54 today. Compare to current time 15:00 - the risk update is now late.

open CWA which causes manual risk update at 15:05 Settings > Google > COVID-19 exposure notifications shows "Last checked for potential exposure on today at 15:05"

adb shell dumpsys jobscheduler shows the following, and the (planned) Run time was not affected by the manual update.

JOB #u0a379/63: 406e72d de.rki.coronawarnapp/androidx.work.impl.background.systemjob.SystemJobService u0a379 tag=job/de.rki.coronawarnapp/androidx.work.impl.background.systemjob.SystemJobService Source: uid=u0a379 user=0 pkg=de.rki.coronawarnapp JobInfo: Service: de.rki.coronawarnapp/androidx.work.impl.background.systemjob.SystemJobService Requires: charging=false batteryNotLow=true deviceIdle=false Extras: mParcelledData.dataSize=180 Minimum latency: +23h59m59s958ms Backoff: policy=0 initial=+1m0s0ms Has early constraint Required constraints: BATTERY_NOT_LOW TIMING_DELAY [0x80000002] Satisfied constraints: CHARGING BATTERY_NOT_LOW DEVICE_NOT_DOZING BACKGROUND_NOT_RESTRICTED WITHIN_QUOTA [0x3400003] Unsatisfied constraints: TIMING_DELAY [0x80000000] Doze whitelisted: true Tracking: BATTERY TIME QUOTA Implicit constraints: readyNotDozing: true readyNotRestrictedInBg: true Standby bucket: ACTIVE Enqueue time: -19h31m42s177ms Run time: earliest=+4h28m17s781ms, latest=none, original latest=none Last run heartbeat: 0 Ready: false (job=false user=true !pending=true !active=true !backingup=true comp=true)

If CWA carried out a manual risk update due to it being opened by the user, wouldn't it make sense for the automated update time to get reset, so the next automated update took place 24 hours later? Also it would be helpful as an enhancement for the CWA UI to show when it next plans to carry out an automated risk update if there is no user interaction in the meantime.

[heinosahling]

@SebastianWolf-SAP asked for affected devices.

Mine ist the Honor View 20 with the latest patches "Priorisierte Hintergrundaktivität" is turned on

Same problem "I've checked the entries under Settings --> Google --> COVID-19 Notifications. They don't get updated until I open the app again."

Pleased let me know If I can support you. Of course I might test a fix.

[NKarolak]

I have some news from my Samsung Galaxy S10e. After I had set "Adaptive Battery" and "Standby for unused Apps" to false, the COVID-19 Notifications got automatically updated after 24 hours. The "Standby for unused Apps" seems to be the critical point. I've just enabled "Adaptive Battery" back to true to verify tomorrow that it will still work, hopefully.

What is also interesting about "Standby for unused Apps": the setting allows to declare apps as exceptions from the standby. However, the Corona-Warn-App is not listed there, meaning, I cannot add it as an exception.

[Edit 02.08.20] My assumption was right. The "Adaptive Battery" setting does not have any negative influence on the app and thus can stay active.

[NKarolak]

@heinosahling And I can tell about my partner's Honor View 20 on Android 10.1: The notifications get updated in the background since he has set the following: Battery --> App Start -->disable "Corona-Warn-App" --> new page: let all three entries active.

[heinosahling]

@NKarolak Thank you! Just activated the suggested setting. Will see the result tomorrow (Hope I remember not to start cwa manually 🤣). Will report here.

[bersbersbers]

@SebastianWolf-SAP

So please keep on posting the devices which still face the issues. We are taking them into account in further test efforts.

Huawei P30 here. App version is 1.1.1, recommended settings applied in the app after the latest update. Never manually tinkered with battery settings anywhere. Still, in Settings - Google - COVID-19 Exposure Notifications, I read

Last checked for potential exposure July 30 at 07:59

That is >3 days ago. I have now applied the setting from https://github.com/corona-warn-app/cwa-app-android/issues/933#issuecomment-667570667 and will wait and see if that resolves the issue without having to open the app.

[heinosahling]

No background notification today. But I did not start the app yesterday after activating the setting. Did that now, will report tomorrow.

@NKarolak Thank you! Just activated the suggested setting. Will see the result tomorrow (Hope I remember not to start cwa manually 🤣). Will report here.

[mbleichner]

Same problem on the bq Aquaris X2 (Android One). Using v1.1.1 with PBA turned on. Android Version 10; Security Patch Level 2020/7/1; Build 3.1.1_20200629-1045

"Adaptive Battery" was active; I just now deactivated it for testing and will report back if it changed anything.

Edit: adaptive battery settings seems to have no effect - the app only updated after starting manually.

Edit²: This night I got a "weekly reminder notification" and the logs showed a successful exposure check at 1:41am. So it looks like it's actually working, though I'm a bit confused that it's been ~40 hours between checks.

[speedy-1702]

Same problem on the Fairphone FP3, CWA v1.1.1 with PBA on Android 9 / GPS 20.26.14

[organistkrieger]

Same problem here on Xiaomi Mi A3. CWA v1.1.1, PBA on. Android 10, latest security patches.

BTW: Android One

[w-flo]

24 + 4 hours after 10:54 is 14:54 today. Compare to current time 15:00 - the risk update is now late.

I still believe the 24+4 "rule of thumb" is incorrect. My phone does automatic risk updates reliably, but it's always around 6pm. Same for my partner's phone, but always at ~9pm. If we open the corona-warn-app at 6am in the morning, it will instantly do the update for that day and obviously skip the automatic update in the evening. Next day, it won't do the automatic background update after 24 hours in the morning at ~6am, but at ~6pm or ~9pm in the evening as it always does. So the time between risk updates is ~36 or ~39 hours in those cases, not 28.

If it's the same for other phones, you can only be sure about failed background updates if a full day from midnight to midnight has gone by without any risk updates.

[MikeMcC399]

@w-flo

I still believe the 24+4 "rule of thumb" is incorrect. My phone does automatic risk updates reliably, but it's always around 6pm. Same for my partner's phone, but always at ~9pm. If we open the corona-warn-app at 6am in the morning, it will instantly do the update for that day and obviously skip the automatic update in the evening. Next day, it won't do the automatic background update after 24 hours in the morning at ~6am, but at ~6pm or ~9pm in the evening as it always does. So the time between risk updates is ~36 or ~39 hours in those cases, not 28.

If it's the same for other phones, you can only be sure about failed background updates if a full day from midnight to midnight has gone by without any risk updates.

What you describe is also what I am seeing: The background update planned time is independent of any foreground risk update that takes place due to opening the app. I hope to get some clarity about what a user can expect through the https://github.com/corona-warn-app/cwa-wishlist/issues/142 , although right now this just a wish-list item. Maybe another wish-list item would be to reschedule the next planned background update to be based on the latest risk update time, whether it was caused by a background or a foreground update? Using the current intervals that would mean the next update would be 24 hours later, not 36 or 39 as in your examples.

Worse case: if a background risk update takes place at 23:59 (Day 1) and two minutes later at 00:01 on the next day (Day 2) the user starts the app, there will be another risk update. I believe that the background risk update scheduled for 23:59 on Day 2 would get skipped due to potentially overstepping the "provideDiagnosisKeys quota" (from API Spec), therefore the next background risk update would be done at 23:59 on Day 3. That would be a gap of almost 48 hours between risk updates! I hope that I am wrong about this.

[gbhajda]

Identische Fehlermeldung beim öffnen der App auf meinem Samsung Galaxy M20 (SM-M205FN) mit Android 10, Corona-Warn-App 1.1.1. In den Geräteeinstellungen ist der Energiesparmodus für die Corona Warn App schon seit einem früheren Problem ausgestellt und in der Corona App ist der Schalter für die priorisierte Hintergrundaktivität an. Bis vorgestern lief alles problemlos, ohne dass seitdem irgendetwas geändert wurde; und ein neustart des Geräts hat auch keinen Einfluss darauf, der Fehler bleibt.

[heinosahling]

No background notification today. But I did not start the app yesterday after activating the setting. Did that now, will report tomorrow.

@NKarolak Thank you! Just activated the suggested setting. Will see the result tomorrow (Hope I remember not to start cwa manually 🤣). Will report here.

Waitet a bit longer because of the 24+4 discussion. No background notification since 02.08. 17:48.

I wonder why it works on @NKarolak s mobile...

[NKarolak]

@heinosahling My partner's phone ;-)

I was in the very same situation like you: Another user reported for my phone that the CWA update already fixed the issue. But this did not work for me because I had additional settings that the other user's (friend/family) phone apparently had not: Standby for unused apps

There must be some similar advanced battery setting active on your phone. My boyfriend is not using any special battery settings since the battery on the Honor View 20 is awesome all by itself (as he says) :-)

Edit: Are you aware of https://www.coronawarn.app/de/faq/#no_risk_update and (linked there) https://slack.com/intl/de-de/help/articles/360001562747-Bekannte-Probleme-mit-Android%E2%80%91Benachrichtigungen?

[bersbersbers]

Last checked for potential exposure July 30 at 07:59

I have now applied the setting from #933 (comment) and will wait and see if that resolves the issue without having to open the app.

It did not (without manually opening the app), I'm still at "July 30 at 07:59". After opening the app, the update worked fine: it's now at "today at 09:29". I closed all apps again (App overview -> recycle bin) and am eager to see when the next update happens.

[DooMMasteR]

For me it seems to be working now, August 1. to 4. all got checks in the google api log.
My phone is a Xiaomi Mi 8 with MIUI 11.0.5.

[bersbersbers]

I have now applied the setting from #933 (comment)

After opening the app, the update worked fine: it's now at "today at 09:29". I closed all apps again (App overview -> recycle bin) and am eager to see when the next update happens.

Just now, it was at "yesterday at 06:27". So it has updated, but again, more than 24(+4) hours ago. I remember opening the app yesterday night, which did not trigger an update apparently - not sure is that should have an effect.

Anyway, let's hope 1.2.0 has something so say about this :)

[organistkrieger]

Same problem here on Xiaomi Mi A3. CWA v1.1.1, PBA on. Android 10, latest security patches.

BTW: Android One

UPDATE: Did not open the app since 3rd August. Today I looked into the Einstellungen->Google->Covid-19-Benachrichtigungen->Überprüfungen..... Here are the results: entries for 3. August 14:57 (when I lastly opened the app); 4. August 16:57 (26 hours from then); 5. August 17:27 (24,5 hours) and today 17:22, which is 23 hours and 55 minutes from yesterday. So for me it kinda seems to work. Hope this helps someone.

[daimpi]

@vaubaehn

Maybe it is possible to ask Google, to implement a scheduled task to the ENF, that triggers the registered exposure notification app (for us: CWA) to run every couple of hours per day? Is something like this technically possible?

I read about the following improvement in the ENF: "App force-stop improvements: if an app has been force-stopped in the background, the Exposure Notifications service will wake it up again automatically." in the Exposure Notifications release notes . Is this functionality doing what it is described to do, and if yes, why isn't that enough to solve the issue? Does anybody know?

@MikeMcC399 It looks like this is functionality is being implemented: https://github.com/corona-warn-app/cwa-app-android/pull/947 🙂

[MikeMcC399]

@daimpi

I read about the following improvement in the ENF: "App force-stop improvements: if an app has been force-stopped in the background, the Exposure Notifications service will wake it up again automatically." in the Exposure Notifications release notes . Is this functionality doing what it is described to do, and if yes, why isn't that enough to solve the issue? Does anybody know?

@MikeMcC399 It looks like this is functionality is being implemented: #947 🙂

According to the Release Notes for 1.2.0 there are two changes which mention the WakeUpService:

• Re-schedule jobs if they were killed and the app was woken up by the WakeUpService https://github.com/corona-warn-app/cwa-app-android/pull/972
• Added key retrieval logic in app's onCreate to include Googles WakeUpService https://github.com/corona-warn-app/cwa-app-android/pull/947

I haven't seen Version 1.2.0 published on Google Play Store yet. It is still showing Version 1.1.1. Has anybody seen a planned publication date?

[daimpi]

I haven't seen Version 1.2.0 published on Google Play Store yet. It is still showing Version 1.1.1. Has anybody seen a planned publication date?

It has probably already been pushed to Google, but it always takes a while to go through the process there until it actually shows up in the play store. My guess would be that it arrives there sometime later today :).

[digundi]

Version 1.1.1 is installed since last week and “prioritized background activity” is set to on. Today I clicked on my risk status and saw that the last update was two days a

sorry i write here, but found no other place to come in. Similar problem: app has its 1.1.1, akku-optimierung is off. my app shows me one risk (green) since over 4 weeks now. Should have disappeared after 14 days, right? No second one up to now. Does it still work? Actualisierung every day works..hope to find back here for the answer later. I am an old women, who was in the end sent here after much trying to answer this question at the usual places... :-)

[thomasaugsten]

@digundi We are working on this and will fix this soon https://www.coronawarn.app/de/faq/#status_14

The app is working correctly please ignore this 1 risk until we fix this.

[digundi]

vielen Dank und many thanks :-)

[vaubaehn]

I haven't seen Version 1.2.0 published on Google Play Store yet. It is still showing Version 1.1.1. Has anybody seen a planned publication date?

It has probably already been pushed to Google, but it always takes a while to go through the process there until it actually shows up in the play store. My guess would be that it arrives there sometime later today :).

Hi @daimpi , I'm replying here to your Gitter question 😉, but it also fits here in this context.

My Playstore on phone actually shows 6/8/2020 as update date, but is only offering v1.1.1. Playstore on desktop browser shows July 20th though. I guess it was indeed pushed to playstore, but is either still on hold by dev team (if this is possible?) for testing purposes, or the checks from Google are still not finished... I somehow remember that somewhere in Google's ENF documentation was mentioned that checks of all Corona apps get special treatment for security after publishing to the store.