New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exposure log was not checked since almost a week #104
Comments
I'm having the same issue on two separate devices. The last check was on 27th June on both devices. Opening the app did not trigger the sync either, both devices as well. Device 1:
Device 2:
|
Same here |
Spostrzeżenie - od ponad tygodnia aplikacja ProteGO Safe nie otrzymała do dystrybucji ANI JEDNEGO klucza Temporary Key. Zbieżność dat może ale nie musi być przypadkowa. Najnowszy plik dystrybuowany przez https://exp.safesafe.app/ ma następującą definicję:
|
It’s probably related to corona-warn-app/cwa-app-ios#740 (comment) |
I have the same issue. |
Exposure Notification analysis is running only when new batches from exp server are available. |
@kamil98 as @lukasz-szyszkowski wrote - EN analysis is done only when there is sth to analyze. In case there is no new keys from positivly diagnosed users there is nothing in logs. Can you check latest statistics if you can see some logs? We had couple of new uploads done so you should see some checks recent days. If so can we please close this issue? |
@pkleczko Hi, you're right, it makes sense that nothing is synced when there are no new keys on the server. But it still doesn't explain why the synchronization didn't work in this case: #104 (comment) It only worked after I've opened the app. I think it's related to: corona-warn-app/cwa-app-ios#740 (comment) I believe that every time after the phone is rebooted I have to open the app manually or otherwise I won't be notified about a possible exposure. |
Describe the bug
My exposure log was not checked since almost a week.
Expected behavior
I thought that my exposure log will be checked every 24h.
Screenshots
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: