search

corona-warn-app / cwa-app-android

Native Android app using the Apple/Google exposure notification API. The CWA development ends on May 31, 2023. You still can warn other users until April 30, 2023. More information:
https://coronawarn.app/en/faq/#ramp_down
Apache License 2.0
2.44k stars 495 forks source link

Vaccination Certificate disappears from UI #3549

Closed vaubaehn closed 2 years ago

vaubaehn commented 3 years ago

Avoid duplicates

Technical details

Describe the bug

Since vaccination DCCs can be imported into CWA, I found several reviews in Google Play Store, that the certificate "vanishes" by itself. According to the following report, it's still persisted, but not displayed:

Ich muss mein impfzertifikat täglich neu hinzufügen, da es einfach verschwindet... Nehm ich den digitalen impfausweiss halt lieber doch analog mit... Update: ich bin kein Idiot. Das Zertifikat fehlt. Aber Plot Twist: wenn ich es nochmal hinzufügen will kommt das es schon da ist. Ist also ein reiner GUI Glitch...

Steps to reproduce the issue

  1. Import/scan vac DCC
  2. Wait some time (till next day), find it vanished
  3. Try to re-import DCC
  4. See error: Already scanned.

Expected behaviour

The DCC should be displayed always after it was persisted.

Additional context

I hope for your understanding, that I create an issue for a bug that I don't experience myself. But as I already found quite a few reports of this kind, I thought could be good to track it here. Please have a look to Play Store reviews yourself. Maybe that issue is already known to the dev team, but then we have a place to track progress from here.

Edit: More reports Screenshot_2021-06-25-10-07-32~2 Screenshot_2021-06-25-10-14-19~2 Screenshot_2021-06-25-10-19-33~2 Screenshot_2021-06-25-11-11-44~2

Internal Tracking ID: EXPOSUREAPP-8117 [Android] Vaccination certificate suddenly disappears Internal Tracking ID: EXPOSUREAPP-8113 Android, after update to 2.4 Internal Tracking ID: EXPOSUREAPP-8114 Ios, after update to 2.4

Shagonaut commented 3 years ago

iOS here. I have the same problem.

Ein-Tim commented 3 years ago

@Shagonaut

Did you update to version 2.4? The certificate has moved to it's own tap, "Certificates".

Shagonaut commented 3 years ago

@Ein-Tim Thanks for your response! Had no automatic update or information in the overview. So I checked manually and yes, it weren't updated to 2.4. - Updated it and now the certificate is visible again. Thank you!

vaubaehn commented 3 years ago

@Shagonaut

Updated it and now the certificate is visible again.

So, there was a problem with iOS also... Interesting. For Android I didn't find any bug fix or similar for version 2.4.x. So, please report back here in case your certificate vanishes again.

Thank you!

Ein-Tim commented 3 years ago

@vaubaehn

I assume there was no bug but it's only bad UX that the register your certificate box is still shown even after you have already added your certificate. This is(was) quite confusing.

vaubaehn commented 3 years ago

@Ein-Tim I was also thinking about this, but if you read above reports carefully, it does not seem to be the case (mostly the first one 😉 ) It does also not fit to what @Shagonaut reported, that after the update the DCC was displayed again

Also: the register your certificate card is below the DCC card... And the DCC card directly under the risk card... So it is quite obvious when it's missing.

Ein-Tim commented 3 years ago

@Shagonaut

Are you sure that under the risk card there was no certificate shown? Or did you only see the "Register your certificate" box?

vaubaehn commented 3 years ago

@Ein-Tim And if people report, for 2 days everything was fine and then the DCC was gone, then there was "a change". That smells more like a technical bug, rather than problems with biological memory.

MikeMcC399 commented 3 years ago

@vaubaehn

That smells more like a technical bug,

That is my feeling too, because the "Digital Proof of Vaccination" tile (if shown) is directly below the risk tile and above the "Register Your Test" tile so it would be hard to overlook.

Ein-Tim commented 3 years ago

That smells more like a technical bug, rather than problems with biological memory.

At least under iOS I disagree. Just take a look here where a user didn't found the vaccination certificate but only the box to register a new one. It was bad UX, and I will later provide a screen recoding which shows this.

vaubaehn commented 3 years ago

At least under iOS I disagree. Just take a look here where a user didn't found the vaccination certificate but only the box to register a new one. It was bad UX, and I will later provide a screen recoding which shows this.

But even for iOS I understood it to be a bug of not updating the home screen, thus not showing the DCC card at all. It needed a "hard close"/force stop and restarting of CWA for some users for the card to show up again, see here: https://github.com/corona-warn-app/cwa-app-ios/issues/2969#issuecomment-863852827 and also for the user you referenced, he did the same: https://github.com/corona-warn-app/cwa-app-ios/issues/2969#issuecomment-863897684 and in both cases it took a while until the card showed up... That's how I understand it 🤔

Updating CWA like @Shagonaut did has the same effect. But I thought we'd try to figure out, what's going wrong on Android? 😄 Could both OS issues really be connected?

Ein-Tim commented 3 years ago

But I thought we'd try to figure out, what's going wrong on Android? 😄 Could both OS issues really be connected?

No. And even if, under iOS it seems to be fixed in version 2.4. So it's only about Android and whether version 2.4 still has this issue.

vaubaehn commented 3 years ago

No. And even if, under iOS it seems to be fixed in version 2.4

Can you reference a PR? That could help, to find out, what was the reason for the home screen not to show the card. Or do you assume this because of @Shagonaut 's experience?

Ein-Tim commented 3 years ago

@vaubaehn I assume this because the logic has changed with the move of the certificate to it's own tab (and because I don't think there was an issue under iOS - I'll come back to you via Slack).

vaubaehn commented 3 years ago

@mtwalli @harambasicluka This issue is originally about DCC card "sometimes disappearing from home screen" with CWA 2.3.4

I'm assuming that

I'm trowing my dart towards two different theories, what could have happend:

Theory A Some data that the UI relies on (or even UI states) is intentionally or accidentally stored in Android's cache, i.e. inside the CWA-cache-directory. When Android OS decides to clean up the cache automatically (due to lack of free memory) the data is lost. I stumbled across this at first, after my CWA crashed from time to time, and my activated debug log feature occasionally reset itself. Discussing this issue with @d4rken (DON'T READ HERE IF YOU'RE ON VACATION), it turned out that debug log stores by design the log inside the cache directory. And because my family-in-law loves to send cat videos via whatsapp, my old phone's memory has a hard time, resulting in automatic cache sweeps, and in this case loss of debug log. If other CWA data is stored there, for some CWA users it may have unexpected results when the cache is cleared. Accidentally storing data inside cache could be due to a wrong storing path constant, or chosing the wrong interface/class for storing in some place.

Theory B A worker is used to process and/or store data. While the worker is still initializing, data is already updated in the process flow and a new worker is going to be started for processing/storing the updated data. As same class workers are blocked as siblings and cancelled, this may result in data loss for the updated data, in case this special (race) condition is not handled gracefully (which is not trivial at all, I guess). This actually happens. While recently checking my debug logs, I found several entries where workers have been cancelled due to siblings (a probably related issue: https://github.com/corona-warn-app/cwa-app-android/issues/2880#issuecomment-832166500, find associated logcat here: https://github.com/corona-warn-app/cwa-app-android/issues/2880#issuecomment-827846585). The maximum number of siblings was always 1. But most of the time, no siblings were existing. This is why I assume, this may mostly affect old and slow devices under high work load, when workers cannot be started fast enough.

In some ways these unexpected behaviours of "disappearing data" may also fit to following issues: https://github.com/corona-warn-app/cwa-app-android/issues/2986 (event not persisted) https://github.com/corona-warn-app/cwa-app-android/issues/2880 (possible worker concurrency/race condition?) https://github.com/corona-warn-app/cwa-app-android/issues/3093 (UI state "lost"/not persisted? vs. ENS API timeout)

A short feedback would be appreciated, thank you.

vaubaehn commented 3 years ago

Now after people updated to 2.4.x (consciously manually or unconsciously automatically) there are new reports of problems:

It's confusing, that only some people are affected. Either their DCC JSON is not fully compatible with schema and the adjustments for validation of DCC implemented into 2.4.x broke it, or there is indeed a problem with storage (see above).

Edit: After a second look, for the first report it's not fully clear whether person tried to scan a QR for a test maybe...

In general I'm voting for better UX in future, in case cards are moved from home screen into a different tab or a menu (e.g., risk card, test registration, statistics, event creation...). The card that is moved could be replaced by a placeholder, that informs user that the function has been moved and where to find it. After tapping on it once, it could be dismissed/removed.

Ein-Tim commented 3 years ago

A 'full' valid vaccination turned to 'valid in 0 days' which looks like data corruption.

For me this sounds like a vaccination certificate which was shown as "fully" valid on day 14 after the last dose already turned into the certificate that is valid in 0 days. This would be a side effect of the fix for https://github.com/corona-warn-app/cwa-documentation/issues/638

In general I'm voting for better UX in future, in case cards are moved from home screen into a different tab or a menu

Could you maybe open a wishlist item for this, please? I fully support this!

DerVogel2020 commented 3 years ago

In general I'm voting for better UX in future, in case cards are moved from home screen into a different tab or a menu (e.g., risk card, test registration, statistics, event creation... The card that is moved could be replaced by a placeholder, that informs user that the function has been moved and where to find it. After tapping on it once, it could be dismissed/removed.

I also missed my certificate after updating. A hint where to find it now would have been nice.

For a wishlist issue it's IMHO too late now, since the vaccination certificate now have been moved to the new tab.

Ein-Tim commented 3 years ago

@DerVogel2020

Yes, for the vaccination certificate you're right, thats too late now. But they did the same with the contact diary back then, so maybe a more general wishlist issue requesting better information if there is an UI change?

Ein-Tim commented 3 years ago

@MDXDave

Please click on the vaccination certificate which you have already added, there you can add the one you got with your second dose.

You can register tests on the home screen, for which you now can request a test certificate.

PS: In version 2.4 you are still only able to register the certificate from one person.

MDXDave commented 3 years ago

Sorry, I thought it should be able to register certificates for more than one person already. 😄

d4rken commented 3 years ago

We need to take care not to mix 3 different issues. "cert disappearing" is just a symptom, possible causes seems to be:

  1. UI Change (not an error?)
  2. Missing but can't be readded (UI error?)
  3. Missing and can be added again (storage error?)

I'm struggling to narrow this down. Would be great if someone could provide a debug log. At least case 2 seems to be a continuous situation that should make a debug log possible.

d4rken commented 3 years ago

TL;DR Can't reproduce yet, still looking into it.

Writing things down helps me think through stuff, thought it might more interesting to put it here than on an internal ticket.

https://github.com/corona-warn-app/cwa-app-android/issues/3549#issuecomment-868530829

Theory A

Couldn't find anything like this (cache theory).

Theory B

Plausible, but I find it unlikely. I don't think workers are the issue here. We don't use workers for immediate in-app action, just reliable background processing. Scanning a certificate moves it immediately into the repository. If the user saw the certificate, that has happened.

https://github.com/corona-warn-app/cwa-app-android/blob/25403e0e90c2ca1534a198a84380afdbb65c7672/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/covidcertificate/vaccination/core/repository/VaccinationRepository.kt#L44

It's then part of the HotDataFlow which is designed to handle the race-conditions while the order can be jumbled, it only uses functions to update the data so we never overwrite data in a race condition new = function(old)

Storing to disk happens async though: https://github.com/corona-warn-app/cwa-app-android/blob/25403e0e90c2ca1534a198a84380afdbb65c7672/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/covidcertificate/vaccination/core/repository/VaccinationRepository.kt#L62-L74

It just listens to every change that happens to the in memory data and saves it. I don't see how a racecondition could break this. It could break and produce the described user behavior if we don't write the data or writing it fails. Not writing would mean that the user kills the app session, or the app crashes (no user mention?) before data is written. But that would only be reasonable if the write operation is delayed long enough for the app session to die (a write takes miliseconds). This could happen all threads in coroutine context are in use (the coroutine is starved). If we had used Dispatcher.Default I maybe could see that happen on low end dual core devices? (Default is ~ amount of cores), but the writer here uses the IO dispatcher which will just create new threads if needed.

This leaves an error during writing the data to storage. Any error would crash the app though (re throw in the catch clause and we are on AppScope). Some research shows that SharedPreferences doesn't really throw many exceptions though... Throwing an error here would be nice, but an error, so low level in Android code, not sure what the app could do about that.

In some ways these unexpected behaviours of "disappearing data" may also fit to following issues:

2986 (event not persisted)

Also strange but different storage mechanisms, checkins use SQL database, SQL database operations are also not shy about throwing errors on low storage. Will write down to check error handling there though, maybe there was an error but it wasn't surfaced.

2880 (possible worker concurrency/race condition?)

Still unclear on causes, don't think it's related.

3093 (UI state "lost"/not persisted? vs. ENS API timeout)

Not related, afaict mostly bad UI behavior due ENS API calls taking minutes instead of miliseconds. Not sure on cause yet. Seems also in the area of weird ENS behavior, a bit like #2880?

harambasicluka commented 3 years ago

PR: https://github.com/corona-warn-app/cwa-app-android/pull/3742

Ein-Tim commented 3 years ago

Here's a Twitter user reporting this behavior: https://twitter.com/Pterodactylus2/status/1420461784314564613?s=20.

She updated the CWA from v 2.4 to 2.5 and the certificate disappeared.

dsarkar commented 3 years ago

@Ein-Tim Thanks. Information will be forwarded.

heinezen commented 3 years ago

Our official recommendation is to restart the device if something like this happens.

Corona-Warn-App Open Source Team

Ein-Tim commented 3 years ago

@heinezen The Twitter user tried a restart and it did not help.

mtwalli commented 3 years ago

@Ein-Tim can we get a log report from any of the users by any chance?

vaubaehn commented 3 years ago

@mtwalli @d4rken I'm beginning to wonder, if the setup/combination of all components may lead to problems with Kotlin's flow, resulting in problems to receive the emits in some cases... Most likely not exactly like the issue described here, but something kind of... I remember the problems with R8 from last year (app crash just for a few java implementations)... Maybe the issue here is a similar edge case?

@Ein-Tim can we get a log report from any of the users by any chance?

Maybe @dsarkar and @heinezen can ask the Android Play Store team to get more affected users for a log report? But according to most of the reports the issue occurs after any update. So users would need to enable error report before the next update and send the report after... Edit: Forget about the last sentence above. A single point error log after the issue occured would already help to understand, what CWA is "seeing" when trying to map the certificates.

d4rken commented 3 years ago

I'm beginning to wonder, if the setup/combination of all components may lead to problems with Kotlin's flow, resulting in problems to receive the emits in some cases... Most likely not exactly like the issue described here, but something kind of... I remember the problems with R8 from last year (app crash just for a few java implementations)... Maybe the issue here is a similar edge case?

The delivered APK (including code shrinking) is the same for all users. If such an R8 related issue would exist, it would affect all users. It's likely a racecondition. Less likely but plausible an edge case specific to the users data. But all data paths I checked, would not have silently thrown the data away when this happen, they would have crashed the app.

Maybe @dsarkar and @heinezen can ask the Android Play Store team to get more affected users for a log report? But according to most of the reports the issue occurs after any update. So users would need to enable error report before the next update and send the report after... Edit: Forget about the last sentence above. A single point error log after the issue occured would already help to understand, what CWA is "seeing" when trying to map the certificates.

Users on Google Play have already been asked, before the update rollout.

I don't think it's an update issue, the update is just a guaranteed app restart after which there is a chance again to reach the problematic state.

An error log from someone who doesn't see the vaccination certificate, but also gets an error message when trying to scan it again, would help the most to further debug this.

@Ein-Tim's Twitter user is still on 2.5.1, it's possible that the performance improvements in 2.6.x successfully mitigate the issue 🤞 .

vaubaehn commented 3 years ago

Hi @d4rken , thanks a lot for your thorough replies! There is not much more to say (than thank you for being on), just sharing some final(?) thoughts:

We need to take care not to mix 3 different issues. "cert disappearing" is just a symptom, possible causes seems to be:

  1. UI Change (not an error?)
  2. Missing but can't be readded (UI error?)
  3. Missing and can be added again (storage error?) I'm not 100% sure whether Cause#2 isn't actually Cause#1. Was something like "adopt sdcard as internal storage" used?

From all reviews in Google Play Store, there were indeed many cause#2 is actually cause#1. But there were obviously also distinct cause#2 cases. I guess cause#3 is quite unlikely, except for users with "throw-everything-on-external-SD"-OS...

Theory A

Couldn't find anything like this (cache theory).

I explicitly tried to wipe cache - but all certificates stayed where they should.

It's then part of the HotDataFlow which is designed to handle the race-conditions while the order can be jumbled, it only uses functions to update the data so we never overwrite data in a race condition new = function(old)

Storing to disk happens async though:

https://github.com/corona-warn-app/cwa-app-android/blob/25403e0e90c2ca1534a198a84380afdbb65c7672/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/covidcertificate/vaccination/core/repository/VaccinationRepository.kt#L62-L74

It just listens to every change that happens to the in memory data and saves it. I don't see how a racecondition could break this. It could break and produce the described user behavior if we don't write the data or writing it fails. Not writing would mean that the user kills the app session, or the app crashes (no user mention?) before data is written. But that would only be reasonable if the write operation is delayed long enough for the app session to die (a write takes miliseconds). This could happen all threads in coroutine context are in use (the coroutine is starved). If we had used Dispatcher.Default I maybe could see that happen on low end dual core devices? (Default is ~ amount of cores), but the writer here uses the IO dispatcher which will just create new threads if needed.

Hmmm... HotDataFlow + IO-Dispatcher + R8 minifiedEnabled = true => https://github.com/Kotlin/kotlinx.coroutines/issues/2835

But then:

The delivered APK (including code shrinking) is the same for all users. If such an R8 related issue would exist, it would affect all users

The reason why I thought, that such an issue has a chance to only affect a limited number of users was this: https://github.com/corona-warn-app/cwa-app-android/issues/1609 What if the compiled byte code here does not result in an app crash but in a NOP for their VMs? Maybe we should ask affected users for their chipset? 😉 But right, this time it's not limited to Android 7 and thus unlikely the cause of this issue. Edit: and a proof, that it's not related to the compiled byte code just comes to my mind: many users reported to get their DCCs reappearing by just "using the UI" (pressing buttons etc), which definetely has no influence on byte code...

It's likely a racecondition.

I hope you win the race! 🏎️ 🤞

Have a nice week! 🍻

Ein-Tim commented 3 years ago

@Ein-Tim's Twitter user is still on 2.5.1, it's possible that the performance improvements in 2.6.x successfully mitigate the issue 🤞 .

@d4rken

I asked the Twitter user and she said that the certificate was still not there.

@Ein-Tim can we get a log report from any of the users by any chance?

@mtwalli

I can ask them! Please let me know in which situation exactly they should start logging and what they are supposed to do while the error log is running.

vaubaehn commented 3 years ago

Hi @mtwalli ,

recent comment from Matthias (who may be on well-deserved vacation?) above:

An error log from someone who doesn't see the vaccination certificate, but also gets an error message when trying to scan it again, would help the most to further debug this.

I found that one on Google Play Store: ID D2EC482DDF153608FCE8

Just in case, it's still useful. Report was on August 3, so only some days left to check it.

Cheers, v.

vaubaehn commented 3 years ago

@Ein-Tim

I can ask them! Please let me know in which situation exactly they should start logging and what they are supposed to do while the error log is running.

Until we don't hear anything different from @mtwalli :

  1. Start error log any time
  2. Go to certificate screen
  3. See no certificates
  4. Try to re-scan a certificate that was previously scanned
  5. See error message
  6. Maybe: close the app ("swipe app away" (depending on OS/MUI) or from app selector (rectangle) in Android navigation), then restart the app and repeat steps 2 to 5
  7. send error log

Release 2.7 will get extended error logging to hunt the bug: PR https://github.com/corona-warn-app/cwa-app-android/pull/3901 fingers crossed! 🤞

Ein-Tim commented 3 years ago

@vaubaehn Okay, thank you! I'll try to get in touch with the user and let you know when I have news.

dsarkar commented 3 years ago

@vaubaehn Thanks for mentioning the error ID. This has been added to the internal ticket some days ago. However, we will ping some devs again.

Ein-Tim commented 3 years ago

@vaubaehn

Bad news, the Twitter user did not keep the sheet of paper with the QR-Code on it, so there is no way for her to rescan the certificate... 😕

FloSchwalm commented 3 years ago

I just experienced this issue. In my case the cause seemed to be Lie-fi - phone was connected to cell, but no data actually getting through. The workaround in my case was to activate airplane mode and restart the app, then the certificate was displayed again. Is there some kind of data update happening that prevents the UI from displaying the certificate while waiting for a response?

vaubaehn commented 3 years ago

@FloSchwalm @mtwalli (and @d4rken 😢 )

I just experienced this issue. In my case the cause seemed to be Lie-fi - phone was connected to cell, but no data actually getting through. The workaround in my case was to activate airplane mode and restart the app, then the certificate was displayed again. Is there some kind of data update happening that prevents the UI from displaying the certificate while waiting for a response?

Looks like the most promising feedback until now: The value sets are part of the flow . What, if there was a connection problem (switching/loosing network, timeout...) when polling for value sets? Can we be sure that this condition is handled properly while being online? Or can it get stuck somewhere (error not handled as expected), and emitting of value set is blocked somehow? Re-starting the app like @FloSchwalm did could handle any race condition (which should not occur in flow). But being in airplane-mode could CWA force to pull an already stored value set...

Edit: this seems especially realistic, as for many users the certificates disappear after an update (network/system congestion due to higher level of activity?)

dsarkar commented 3 years ago

@vaubaehn @FloSchwalm Thanks for discussing here: Forwarded to internal ticket, pinged dev team.

d4rken commented 3 years ago

@FloSchwalm's issue has the same symptoms but maybe not the same cause. You are on v2.7.x? :thinking:

I looked into the network situation. We can simulate a stuck network situation by adding an interceptor with a thread.sleep within the client created by HttpModule or just do some firewall shenanigans.

On CWA v2.6.x

The certificates load instant as no network call is involved. The only delay is local processing/rule-checking, nothing significant enough to be called "hanging" (and the debug build is slower than prod anyways). I also artificially restricted the thread pool to see if a hanging network check could starve other coroutines, but the certificates still load quickly.

On CWA v2.7.x

If the locally cached config is outdated, the certificates tab may be empty for up to 10 seconds. This is due to the state being checked for each emission and the state check requiring app-config data: https://github.com/corona-warn-app/cwa-app-android/blob/97fbc95b71db96ed637af3eaa35118eb705a1611/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/covidcertificate/common/statecheck/DccStateChecker.kt#L28

Even though DccStateChecker only requests the currentConfig and doesn't force a check with getAppConfig(), it will still hang if the app was just started and it is the first time the config is accessed.

AppConfigProvider , when initializing, calls AppConfigSource.getConfigData() which will perform a network request if the local config is no longer valid.

So if the app was no longer in memory and the user opens the app (ignores the empty home screen feed which is also waiting for app config data), then the certificates tab will be empty until AppConfigProvider has it's initial value, which in case of bad network would be after up to 10 seconds (timeout, maybe 19 seconds in the absolute worst case scenario). Anything that depends on app-config will be blocked until that initial value is available.

I would probably change AppConfigSource.getConfigData() to something like getConfigData(offlineOnly: Boolean = false) so that it skips the remote config request if set, and then use that to init AppConfigProvider.

Any part of the app that requires the absolute latest config uses AppConfigProvider.getAppConfig() AFAIK, and all components that are fine with the current one, there is no longer the chance to hang in this edge case.

In both 2.6.x and 2.7.x the app hangs for ~5 seconds on the update check and the HomeScreen stays empty, but you can still switch to the cert tab.

So maybe the issue from 2.3 to 2.5 (UI confusion aside) was fixed with 2.6.x, and this is just the same symptom with a new cause?

FloSchwalm commented 3 years ago

Yes, my App version is 2.7.1 Your description definitely fits what I experienced. It's probably possible that I closed the app and moved on to airplane mode before the 10-19 seconds passed as I was supposed to present my certificate and was in a hurry not to hold up the line longer than necessary.

d4rken commented 3 years ago

@FloSchwalm PR #3976 was accepted and your issue should be fixed with 2.9.0. Maybe now the tale of the disappearing certificates will come to end and we will live happily ever after :partying_face:.

Maybe the issue tickets should be split to not mix different causes :thinking:

FloSchwalm commented 3 years ago

Thank you so much, looking forward to the release :)

vaubaehn commented 2 years ago

Still a problem after updates for some users, e.g., https://play.google.com/store/apps/details?id=de.rki.coronawarnapp&reviewId=gp%3AAOqpTOFG0hgrr7ZDtuVbeGY2KU6ZnmSMIZRy9-Ctk98qS46ZyC8LJd39OVKWCt0w5_9KWOQ_6dA99jpmM-qGCA

svengabr commented 2 years ago

I have just checked the linked Jira issue.

Jira Ticket is flagged as: Resolution: Wont Fix Status: Obsolete

Developer comment:

Setting to obsolete, duplicate.

Continue in EXPOSUREAPP-8113

Ein-Tim commented 2 years ago

@svengabr

Whats the status of EXPOSUREAPP-8113?

svengabr commented 2 years ago

@Ein-Tim

EXPOSUREAPP-8113

Status: Analyzing Resolution: Unresolved

Will set this to priority Medium, because only very few users are affected by this behaviour.

Last updated in September 2021

Ein-Tim commented 2 years ago

@svengabr Ok, your call whether to leave this issue closed or reopen it.