cwa-app-ios
cwa-app-ios copied to clipboard
Fehler 13 - problem persists after 24 hrs
My Corona App hasn’t refreshed since a week now, showing the error code „Fehler 13“. Please check.
Internal Tracking ID: EXPOSUREAPP-5836
IOS 15.5 iPhone XR Corona Warnapp Version: 2.24.1
Hey @Anonymous170722
Please, could you enable error logging like this:
- In der CWA auf dem Reiter "Status" ganz nach unten scrollen
- Auf "App-Informationen" scrollen
- Auf "Fehlerberichte"
- Auf "Starten" tippen
- Einmal machen, dass der Fehler auftaucht
- Schritte 1-3 wiederholen
- Auf "Fehlerbericht senden" tippen
- Auf "Einverstanden und senden" tippen
- Nach unten scrollen
- Auf "ID-Historie" tippen
- Die jeweilige ID hier in den GitHub Issue stellen
After you did this, please perform the following steps to fix the problem:
- iOS-Einstellungen öffnen
- Bis zu "Begegnungsmitteilungen" scrollen & "Begegnungsmitteilungen" antippen
- Auf "Corona-Warn-App" ("Aktive Region") tippen
- Auf "Corona-Warn-App" tippen
- Runterscrollen
- "Begegnungsinformationen teilen" deaktivieren
- Etwas mehr als 24 Stunden warten
- Schritte 1-5 wiederholen
- "Begegnungsinformationen teilen" aktivieren
- Oben auf den blauen Text "Als aktive Region festlegen" tippen
- CWA öffnen und prüfen ob alles wieder funktioniert
We need an error report over 24h. Please post the new id in 24h again
Ok, I will send a new report tomorrow. Thank you
@Anonymous170722 Thanks for reporting. please see
https://github.com/corona-warn-app/cwa-app-ios/issues/4676#issuecomment-1186497163
We need an error report over 24h. Please post the new id in 24h again
Internal Tracking ID: EXPOSUREAPP-5836
Best wishes, DS
Corona-Warn-App Open Source Team
hey there, Here’s the new error report ID.
Still not working.
It looks like a network issue Can you access on your phone this urls:
https://verification.coronawarn.app/version/v1 Whitelabel Error Page https://svc90.main.px.t-online.de/version/v1/diagnosis-keys/country/EUR/date List of dates
Identical to: https://github.com/corona-warn-app/cwa-app-ios/issues/4462
@thomasaugsten Seems like there is action required from your side. We now have(I strongly assume) two reports where the user is able to access the websites itself without problem but CWA fails to establish a connection.
No, I am sorry, I cannot open these.
After evaluating the error logs that we got, it seems as if the analysis from https://github.com/corona-warn-app/cwa-app-ios/issues/4462#issuecomment-1122082267 wasn't quite accurate.
The error message Unsupported protobuf type: 4
also pops up here, but the 4
doesn't seem to refer to the Protocol Buffer data type sint32
, but to a lower-level type that when encountered throws the error message in ENF.
We still don't fully understand why this error happens in ENF.
Our assumption is that for some reason, ENF fails to parse the key file, perhaps because the file got corrupted on the device or it fails to correctly load the file into memory. A corrupted key file on CDN seems to be unlikely, because a lot more devices would be affected then.
Our proposal to address this is to clear the cached key files when the error happens such that they are downloaded again next time. This would technically be similar to an in-app reset (with regards to what happens to the key packages then), which usually seems to solve the problem.
@mlenkeit Thanks for sharing your findings! Is there already a plan for with which version this fix will be shipped?
@Ein-Tim https://github.com/corona-warn-app/cwa-app-ios/pull/4684 is in progress and targeted for 2.25 if everything goes as planned; otherwise, it might be delayed to 2.26.
@Anonymous170722
Hey, could you please update to version 2.25 and check if this update fixed the issue?
Hi Tim,
Thank you, my App is working again and checking for potential Covid encounters.
Thanks for helping me!
Von meinem iPhone gesendet
Am 01.08.2022 um 22:31 schrieb Tim @.***>:
@Anonymous170722
Hey, could you please update to version 2.25 and check if this update fixed the issue?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.
Thanks to all participants.
As this was solved in version 2.25, I'm now closing this issue as completed.