Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

Risc assesment stopped at pretty much every start of the app, resolves itself after brief waiting time #1592

Closed
2 tasks done
JMoVS opened this issue Nov 29, 2020 · 6 comments
Labels
bug Something isn't working

Comments

@JMoVS
Copy link

JMoVS commented Nov 29, 2020

  • Bug is not mentioned in the FAQ
  • Bug is not already reported in another issue

Describe the bug

I think I‘m encountering the same issue as this comment #1153 (comment)

But this behaviour is slightly different than the one explained in 1153. the end result is equally bad - my app doesn‘t refresh in the background reliably and only when I open it myself, it then tells me that refreshing did fail (send me a notification when it fails so I can open the app!), then that it‘s refreshing and it‘s fine again. My current hunch is that as I‘m a user who switches on Flightmode every night but the checking times are sometimes during the times where my flight mode is still on, it looks like CWA does not successfully use iOS background refresh to retrigger a check until someone reopens the app.

Expected behaviour

CWA gracefully recovering from a failed check during flight mode at night => checks working reliably

Steps to reproduce the issue

I‘m not sure if it‘s the flight mode but with iOS 14 it has been like this eversince. Have your expected refresh time and set flight mode on before that time. Easiest to test overnight.

Technical details

  • iOS Version: 14.2
  • Device: iPhone SE 2020

Possible Fix

  • Send a notification when the check fails and asking users to open the app!
  • use iOS background refresh to retrigger a check
@JMoVS JMoVS added the bug Something isn't working label Nov 29, 2020
@thomasaugsten
Copy link
Member

Did you test the new v1.7.1 if this version updates in the background reliably on your phone?

@heinezen heinezen added the further input needed Issue requires more input from the creator to be processed good first issue label Nov 29, 2020
@dsarkar
Copy link
Member

dsarkar commented Dec 1, 2020

Dear @JMoVS,

Could you please give us some feedback regarding this issue after updating to CWA version 1.7.1? Many thanks.

Best wishes,
DS


Corona-Warn-App Open Source Team

@JMoVS
Copy link
Author

JMoVS commented Dec 1, 2020

Unfortunetly, I had to get my phone replaced yesterday and it seems like for whatever reason those exposures are not part even of the password encrypted local backup, so I can only really say in a few days when I get my first info in the app

@dsarkar
Copy link
Member

dsarkar commented Dec 1, 2020

Hi @JMoVS, OK, we stand by for your feedback. Best wishes,
DS


Corona-Warn-App Open Source Team

@Mihahn
Copy link

Mihahn commented Dec 1, 2020

I had the same problem and it seems to be resolved in 1.7.1.

@dsarkar
Copy link
Member

dsarkar commented Dec 9, 2020

Hi @Mihahn, @JMoVS, Thanks for all the feedback. We consider this issue as solved. We will close the ticket now. Please feel free to re-open, if necessary. DS


Corona-Warn-App Open Source Team

@dsarkar dsarkar closed this as completed Dec 9, 2020
@dsarkar dsarkar removed the further input needed Issue requires more input from the creator to be processed good first issue label Dec 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants