Cwa-app-ios: ENErrorDomain-Fehler 5

[christianneu]

Avoid duplicates

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

Describe the bug

After opening the app, this error pop up is shown immediately. It pops up 4 times, fast after each other.

Expected behaviour

Status Update of the current screen and data in the background.

Steps to reproduce the issue

1. Open App
2. Wait
3. Popup opens 4 times quickly

Technical details

• iOS Version: 13.5.1
• Device: iPhone XR

[thomasaugsten]

Error code 5 is "Operation is not supported." Do you have special conditions on you phone like profiles, proxy using a second Corona App?

[tkopton]

Same error here. Started today. iOS 13.5.1. Last Update 22.06.2020 22:00
Error repeats when you turn exposure logging off and on again.

[nikf00]

I have the same issue on an iPhone X. Pops up every time I open the app or come back from the “Risiko-Ermittlung“ screen. Restart does not help. Last risk update was 22.06.2020 22:43

[HoSch-193]

Same at my Device. iPhone 8 (iOS 13.5.1), Re-starting bluetooth, app or device doesn´t help. Device is under Mobile Device Management. Last Risk Update 23.06.2020, 13:37

[haosap]

Hi @HoSch-193 ,
You said, your Device under Mobile Device Management? Could you please tell us which MDM are you using? Does it "inject" some special profile to your device?
Thanks.

[haosap]

Hi @tkopton,
Is your device under management of some MDM? Or it is just a normal private device.
Thanks.
cc @ChristianKienle

[HoSch-193]

Hi @HoSch-193 ,
You said, your Device under Mobile Device Management? Could you please tell us which MDM are you using? Does it "inject" some special profile to your device?
Thanks.

Its a companies MDM, a crypt configuration containing a MDM, managed apps, password policy, app-layer VPN-setting, Wi-Fi Networks, Web clips, device identity certificate, further certificates and payloads and a passcode restriction, but no further restrictions.
Private using is allowed.

[HoSch-193]

Hi @tkopton,
Is your device under management of some MDM? Or it is just a normal private device.
Thanks.
cc @ChristianKienle

see comment above

[Calyp798]

I have the same problem on an iPhone 7 (iOS 13.5.1). Last update was 23.06.2020 9:57 AM. Private iPhone and no special profiles.

[jantenne]

Same with me. Unmanaged. iPhone X. 13.5.1. app worked until 23.6. device is not managed.

[DrmedWurst]

Same problem on iPhone 8 Plus, iOS 13.5.1. Last update 22.06.2020. Private device without special profiles.

[thomas-wolf]

Same here for an unmanaged iPhone SE (first generation).

[Launethil]

Same issue for me. Only noticed it today, but according to the main screen the app hadn‘t received any updates for a couple of days.

iPhone 7 (private device, unmanaged)
iOS 13.5.1

[tobse80]

Same error on my device, iPhone SE (1st gen), SW-Version 13.5.1 (17F80). Private device, unmanaged.

[andibergzelfi]

Same error here, iPhone X, iOS 13.5.1, no MDM, VPN or whatsoever

[DanteFiligesto]

Same error iPhone 7, private, 13.5.1
The day count stopped increasing since the error showed up, apparently making the app useless

[FreakyTea]

Same error on my Dads iPhone

• iPhone 7 Plus, company phone (but unmanaged), iOS 13.5.1

[derbesen]

Same error here, it
Started 2 Days ago. iPhone 7, last iOS. Private Phone, no jailbreak, Not managed. No Update singe 2 Days, App useless.

[Dominic3374]

Same here. (IPhone Xr) I wonder If nobody checks its app continuously. Is this error a mass phenomenon?

[Dominic3374]

This is the only thread I find. I found one tweet from another person to it^^

[Dominic3374]

After posting here it worked the first time for 48 hours. It’s back working^^

[flixflax]

Still does not work on my iPhone 11 Pro Max with latest version of iOS and the app. Device not managed. No VPN, no proxy.

[haosap]

Hi @flixflax ,
I assumed that, you have tried to uninstall and install the app again right? If so, we'll also try to report this issue to Apple as well. Because theoretically if you reinstall the app, the state of the app should be also totally reseted.
Thank you.

[Launethil]

Hi @flixflax ,
I assumed that, you have tried to uninstall and install the app again right? If so, we'll also try to report this issue to Apple as well. Because theoretically if you reinstall the app, the state of the app should be also totally reseted.
Thank you.

I tried that yesterday, same problem right away.

[calledCajo]

Same with me. I use iOS13.5.1 on iPhone X, no MDM, no VPN. I deleted the app and reinstalled it. Same issue...

[haosap]

Dear app users,
Thank you so much for your bug report. From our side, we cannot reproduce this errors in our devices. So we'll collect some information and report directly to Apple.

[ideasondesign]

Have the same issue. Private unmanaged phone.
I have tried reinstalling the app, restarting the phone but it didn't fix the problem.

[Kvorra]

Same error message on iPhone 6s. It worked before, now it doesn't update since 23.6.

[DanteFiligesto]

Dear app users,
Thank you so much for your bug report. From our side, we cannot reproduce this errors in our devices. So we'll collect some information and report directly to Apple.

Can the app save error logs and report them to your server? Is there a way one can enable this?

[Filirator]

Same error message on iPhone. No reinstall.

[JudithWe]

Same here: iPhone XR - Software Version 13.5.1

[rbemsel]

Same here: iPhone 11 - Software Version 13.5.1

[AlbertJohann58]

I got the same error message, but now the app asked me to activate tracking.

[JudithWe]

Same here!

[cschwinge]

Same problem - private iPhone 8 (not managed), Software Version 13.5.1

[sysfyg]

Had same message today on iPhone 8. Killed app, restarted app - this time smooth. I do have two entries in contactlist with same time stamp, but one with 503 cases (same number as yesterday) and 720.

see also #778

[calledCajo]

I called the Telekom Hotline. They said that many users reported this issue and they contacted the dev department and are pretty sure a new update will be released near time

[Fadelius]

Same same with iphone 11 pro

[christianbrb]

Hi @flixflax ,
I assumed that, you have tried to uninstall and install the app again right? If so, we'll also try to report this issue to Apple as well. Because theoretically if you reinstall the app, the state of the app should be also totally reseted.
Thank you.

Hi @haosap :) I have got the same issue as well. If I am doing this do I loose my contact tracing information?

[thomasaugsten]

@christianbrb No you will not losing information

[christianbrb]

Maybe this helps to reproduce the issue.

I have played around a little bit with activating and deactivating Wifi and mobile data.

1. When switching from Wifi to LTE I got the EN-Error-Domain 11.
2. When switching back to Wifi I got the 13 two times quickly one after the other which I now get consistently when I open the app.

Related Issue https://github.com/corona-warn-app/cwa-app-ios/issues/759

[HoSch-193]

@christianbrb No you will not losing information

I did so and I lost contact information and bug is still there. So do Not re-install.

[christianbrb]

After the reinstall I still get Error 13. Ok, that’s due to the API rate limitation (https://developer.apple.com/documentation/exposurenotification/enerror/code/ratelimited)

[haosap]

Dear app users,
Thank you so much for your bug report. From our side, we cannot reproduce this errors in our devices. So we'll collect some information and report directly to Apple.

Can the app save error logs and report them to your server? Is there a way one can enable this?

Hi,
Due to the data privacy, we're not allowed to log any information. That's the reason, our dev team is trying to reproduce the bug. At the moment, we could not manage to do it.

[Groman123]

Same issue here on iPhone 11 unmanaged device with iOS 13.5.1

Here is a short video of the issue in the wild.
The message comes up three times on app start and every time you get back to the main screen.

[christianbrb]

@christianbrb No you will not losing information

I did so and I lost contact information and bug is still there. So do Not re-install.

@thomasaugsten I have also lost all the information

[haosap]

Maybe this helps to reproduce the issue.

I have played around a little bit with activating and deactivating Wifi and mobile data.

1. When switching from Wifi to LTE I got the EN-Error-Domain 11.
2. When switching back to Wifi I got the 13 two times quickly one after the other which I now get consistently when I open the app.

Hi @christianbrb ,
Thanks for your tips. But unfortunately, I have followed your instructions and cannot reproduce the error. We have addressed the issue directly to Apple and asked them in which condition the error will be raised.

[thomasaugsten]

@christianbrb What you mean with all information? The contact protocol can only reseted in the iOS settings.
You have to onboard again and the last check date is gone but all keys are still available.

[Fritte911]

I am having the same problem, IPhone 11 Pro, used it for 8 days without any problems now my contact list have no entries.

[kaisemarmuc]

Same problem.
Occurs after clicking on „Aktualisieren“.
IPhone 6s, Software Version 13.5.1.
Error message pops up only once.

[thomasaugsten]

Can somebody update to iOS 13.6 Beta 2 and recheck the error?

https://betaprofiles.com/ios13

[kaisemarmuc]

Can somebody update to iOS 13.6 Beta 2 and recheck the error?

https://betaprofiles.com/ios13
Sorry, I can‘t. Managed profile.

[Launethil]

Can somebody update to iOS 13.6 Beta 2 and recheck the error?

https://betaprofiles.com/ios13

Did the update to test this. Unfortunately still getting the same error and behavior.

[thomasaugsten]

@Launethil can you please contact me directly for a bug report

[Launethil]

@Launethil can you please contact me directly for a bug report

Sure thing. Mail is on its way. :)

[marijoo]

Same with iPhone 11.

[zerbes]

Currently upgrading to iOS 13.6 Beta 2 for testing

[nrd-tx]

Same here
13.5.1 Iphone 7
Message pops up 2 times after openIng the app
Updated last time June 23rd (day before yesterday)

[Hubersan]

Same error here. Started today. iOS 13.5.1. Last Update 22.06.2020 22:00
Error repeats when you turn exposure logging off and on again.

Same error here on iPhone SE (A1723) on iOS 13.5.1, normal private iPhone, not under MDM. No additional Corona App installed.
Error 5 appears when opening the App.

[zerbes]

Upgrade to iOS 13.6 Beta 2 did not help, phone-diagnosis-data was forwarded to @thomasaugsten.

[ronxorange]

Same in SwissCovid app...
with Iphone 11 Ios13.5.1

[DanteFiligesto]

Dear app users,
Thank you so much for your bug report. From our side, we cannot reproduce this errors in our devices. So we'll collect some information and report directly to Apple.

Can the app save error logs and report them to your server? Is there a way one can enable this?

Hi,
Due to the data privacy, we're not allowed to log any information. That's the reason, our dev team is trying to reproduce the bug. At the moment, we could not manage to do it.

This means that if I give you my iPhone you can’t get any information from it to analyze the problem? So I guess you are trying to reproduce using an app version with logging on? If so, can we give it a try and help reproducing? Data privacy should be my choice.

[Filirator]

Next day - same shit. SAP and Telekom are not able to fix the bug???

[Hermann12]

Eine Woche hat es gedauert.
IPhone11
IOS13.5.1
Deinstallation und Neue Installation bringt nichts,
Fehler erscheint sofort wieder.

[GaebRush]

I just reinstalled the app. Interestingly already during the setup process, immediately after it asks to activate the exposure logging, I got the ENErrorDomakn Error 5 again.
I do not have any special setup, the device is an iPhone 8 and it runs iOS 13.5.1. The setup process was done using my device’s mobile data.

[FreakyTea]

Same error on my Dads iPhone

• iPhone 7 Plus, company phone (but unmanaged), iOS 13.5.1

The app just started working again on his phone 🤷🏻‍♂️

[hauspost]

Two iPhones in our household now show this error. iOS is updated, iPhones are 8 and 11 Pro, unmanaged, no special setup. happens in WiFi (Vodafone Kabel) and mobile (Telekom), does not happen while disconnected from internet. Last risk update on 23.06.2020. See photos. Video available as well.

Are there any news on this?

[tkowark]

Next day - same shit. SAP and Telekom are not able to fix the bug???

@Filirator please watch your language. The team is working hard on narrowing down the issue and as you can see in this thread, reproducing it is just not trivial.

[zerbes]

My PiHole-logging shows the domain svc90.main.px.t-online.de tried to be reached which i can´t ping manually as well. No idea if that helps anyhow.

[DisappointedMoose]

Same issue here. iPhone X iOS 13.5.1. Unmanaged phone.

Owner says the error started when came back to Germany from the Netherlands and was connected to a German mobile carrier again.

Other Android and iOS devices in the same network work fine.

[christianbrb]

@zerbes That's great.

The problem went away after deleting and updating the app, but also all data is gone (I'll create a separate issue to analyse that).

I also assume, that the matching is the problem as the first covid90 positive test results have been uploaded and the issue on my iphone only appeared afterwards.

Maybe issue https://github.com/corona-warn-app/cwa-backlog/issues/2 is related.

[Groman123]

y PiHole-logging shows the domain svc90.main.px.t-online.de tried to be reached which i can´t ping manually as well. No idea if that helps anyhow.

I got an answer via ipv4 for that host.

[zerbes]

y PiHole-logging shows the domain svc90.main.px.t-online.de tried to be reached which i can´t ping manually as well. No idea if that helps anyhow.

I got an answer via ipv4 for that host.

Your system pings a IPV4, my tried a IPV6. Interesting to see the different behaviour. The IP 87.140.209.90 can be pinged manually as well here!

[FabBaur]

I had the same problem with the Swiss Covid App. For me, the error disappeared the second I was in contact with another iPhone Swiss-Covid-App User.
Not sure if that helps in any way.

[colu89]

Ive got the same issue. It started about 3 days ago. Iphone 7, 13.5.1. not managed.

[lventimi]

Since three days the same issue.
Reinstalling the App doesn't cure the problem

IphoneSE IOS 13.5.1

[christopher-wilke]

Same Error here. I am using iPhone XR.

[zerbes]

I had icloud-service disabled or at least disabled the different types of data to be forwarded to icloud. Enabling it did not solve the issue for me

[jantenne]

@h3dgyy I have all services active, beside mail, calendar and contact which I drive via exchange

[Filirator]

icloud is enable

[Launethil]

iCloud services were enabled. I disabled them and restarted the phone -- still got the error. Re-enabled iCloud services, restarted the phone -- same problem.

I noticed that it takes "notably" more time for the error to pop up after a restart compared to just shutting down the app and reopening it. Only talking about one or two seconds, but it was long enough for me to think the error might have been fixed after the first restart. That probably means nothing, but I thought I'd mention it, just in case.

[haosap]

Hi @Launethil ,
Thanks for elaborating the issue.
Due to lack the log of the app, we can only try to enumerate all the possibilities. We'll keep investigating the issue.

[auxua]

Same issue here (iOS 13.5.1, no mdm, dev profiles, iphone XR)

It started after some time at place near the belgian border (~1km), where the belgian provider nets where dominating the german ones.

A friend told me the same behavior after some time near the border too.

Are you others also located near to borders?

[Hubersan]

Hi All,

my son is located in the middle of Germany with his unmanaged iPhone SE. No borders anywhere near. I looked into his Kontaktprotokoll and obviously there was never a contact registered (we have at least 3 iPhones with the App in the house hold and 2 at relatives who were visited). My iPhone 8 works just fine, shows 3 contacts and has no error message 5.

Von meinem iPhone gesendet

Am 26.06.2020 um 17:21 schrieb auxua [e-mail]:


Same issue here (iOS 13.5.1, no mdm, dev profiles, iphone XR)

It started after some time at place near the belgian border (~1km), where the belgian provider nets where dominating the german ones.

A friend told me the same behavior after some time near the border too.

Are you others also located near to borders?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[jantenne]

@Hubersan where do you see contacts made? Because I looked into the settings where the protocol should appear and this is empty. I thought it has to be like this. So mine is empty since the first day while I traveled also a lot.

[Filirator]

me too - no contacts since 10 days!

[ST-KW]

Same problem here (unmanaged IPhone SE first gen). My ping answers from Hamburg:

ping svc90.main.px.t-online.de

Ping wird ausgeführt für svc90.main.px.t-online.de [2003:2:20:701:87:140:208:26] mit 32 Bytes Daten:
Antwort von 2003:2:20:701:87:140:208:26: Zeit=11ms
Antwort von 2003:2:20:701:87:140:208:26: Zeit=10ms
Antwort von 2003:2:20:701:87:140:208:26: Zeit=10ms
Antwort von 2003:2:20:701:87:140:208:26: Zeit=10ms

Legacy IP also works:

ping -4 svc90.main.px.t-online.de

Ping wird ausgeführt für svc90.main.px.t-online.de [87.140.208.26] mit 32 Bytes Daten:
Antwort von 87.140.208.26: Bytes=32 Zeit=12ms TTL=53
Antwort von 87.140.208.26: Bytes=32 Zeit=11ms TTL=53
Antwort von 87.140.208.26: Bytes=32 Zeit=12ms TTL=53
Antwort von 87.140.208.26: Bytes=32 Zeit=12ms TTL=53

The problem persists if I disable WLAN and use the app via LTE.

Reboots do not bring any changes either.

[djaegerDe]

Hi, I have the same problem on my private, unmanaged iPhone 11.

My contact protocol is empty, although another person in the household and people in the Office also uses the app and the contact log lists entries on their phones.

I tried disabling and enabling the „Risiko Ermittlung“ and restarted the phone, but this did not help.

I don't know if it helps, but I use Apple Family Sharing for apps and Apple services and this has led to some problems with other apps in the past.

[zerbes]

What do we know until now?

• german and swiss app face the same problem -> not DNS-related (can be resolved and swiss app wobn’t use Deutsche Telekom domain with high probability)

• the problem did not show up on the android version of the app (yet)

• most of the iphone-models supporting iOS 13.5+ show the error ->not model specific

• not iCloud-related

• it showed up spontanousy without any change to the installed app or iOS -> external factor?

Keep up the good work, dev-team, and chase that bug :)

[Hubersan]

Hi All,

on my iPhone 8 everything is fine and under Setttings\Corona-Warn I can go to the bottom (blue text) to see the Covid-19 Kontaktprotokoll - after authentication I see a log of my contacts with timestamp:

On my sons iPhone SE, there is not a single entry. He has this weird „Error 5“.
I suspect, that there is not a small number out there with the App running - but with no effect, because it is virtually disabled.

On my company phone (iPhone SE, managed) I realized, that the App also disables all contact checking silently once the powersaving mode is on. I had accidentially turned it on (76% battery) and wondered why the App showed some kind of disabled state (red WLAN on this comic picture of the contact check). After disabling power saving and restarting the App all was fine. Different topic, but interesting to know.

Cheers,
Peter

Von meinem iPhone gesendet

Am 26.06.2020 um 19:19 schrieb Steffen Zerbe [e-mail]:


What do we know until now?

german and swiss app face the same problem -> not DNS-related (can be solved and swiss app wob‘t use Deutsche Telekom domain with high probability

the problem did not show up on the android version of the app (yet)

most if the iphone-models supporting iOS 13.5+ show the error ->not model specific

it showed up spontanousy without any change to the installed app or iOS -> external factor?

Keep up the good work, dev-team, and chase that bug :)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[Hubersan]

I just read about the Apple family sharing (Familienfreigabe). In our case out of 4 iPhones (SE, 2x8, 6) all work fine - except the SE. All unmanaged. We also use Familienfreigabe.

Von meinem iPhone gesendet

Am 26.06.2020 um 20:13 schrieb Peter Huber [e-mail]:

Hi All,

on my iPhone 8 everything is fine and under Setttings\Corona-Warn I can go to the bottom (blue text) to see the Covid-19 Kontaktprotokoll - after authentication I see a log of my contacts with timestamp:

On my sons iPhone SE, there is not a single entry. He has this weird „Error 5“.
I suspect, that there is not a small number out there with the App running - but with no effect, because it is virtually disabled.

On my company phone (iPhone SE, managed) I realized, that the App also disables all contact checking silently once the powersaving mode is on. I had accidentially turned it on (76% battery) and wondered why the App showed some kind of disabled state (red WLAN on this comic picture of the contact check). After disabling power saving and restarting the App all was fine. Different topic, but interesting to know.

Cheers,
Peter

Von meinem iPhone gesendet

Am 26.06.2020 um 19:19 schrieb Steffen Zerbe [e-mail]:


What do we know until now?

german and swiss app face the same problem -> not DNS-related (can be solved and swiss app wob‘t use Deutsche Telekom domain with high probability

the problem did not show up on the android version of the app (yet)

most if the iphone-models supporting iOS 13.5+ show the error ->not model specific

it showed up spontanousy without any change to the installed app or iOS -> external factor?

Keep up the good work, dev-team, and chase that bug :)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[HoSch-193]

Since 20:25 my App is working again

[christianbrb]

@christianbrb What you mean with all information? The contact protocol can only reseted in the iOS settings.
You have to onboard again and the last check date is gone but all keys are still available.

@thomasaugsten The contact protocol has been deleted with the deletion of the App.

I had ~10 days of contact tracing in the app and now it shows just 1 day.

[thomasaugsten]

@christianbrb This are two different things. Contact protocol is managed by the OS. The App shows how many days in a row it checked the downloaded keys against the contact protocol of the OS.

[christianbrb]

@thomasaugsten Thanks for your reply. I have created #794 to avoid sidetracking the issue.

[christianbrb]

Thinking about the issue, it first appeared on my phone while trying to download and match the first key file. Before the error appeared my “Kontaktüberprüfungen“ always showed 0 entries.

Has anything changed regarding the key data structure from 1.0.0.0 to 1.0.2.2 in the app, in the cwa-server or in the Android (app)?

[hauspost]

The app started working again on my phone yesterday evening. No more errors, and risk status is updated. From my side, no changes or reinstalls were made. The change happened while leaving the Hamburg region for the first time in weeks, driving to Cologne. Can’t imagine how this could be relevant, but who knows...

[christianbrb]

@hauspost The error appeared on my iPhone after significantly changing my location.

Maybe this is related to the region field in the header of exposition_notification.proto message (see https://github.com/corona-warn-app/cwa-documentation/blob/master/solution_architecture.md#data-format)?

[MisterRios]

My app stopped working on Wednesday. I kept getting this same error twice every time I opened the app. I have a Private IPhone 8.

This morning I was poking around in location services after keeping track of the comments here. I switched “Location Based Alerts” (in Settings -> Privacy -> Location Services -> System Services) to On, and then restarted the app. It immediately worked again.

I switched it back to off, and it still works, though who knows what will happen in 24 hours when it tries to update again.

Hope you find and squash the bug soon! Good luck!

[svona-ai]

Same issue here, iPhone XS with 13.5.1 unmanaged. Stopped working with this error about 2 days ago, realized it when traveling from Munich to Frankfurt (but may have stopped working before), had the last status update on 22 June. Deleted the app and reinstalled, still the same issue.

[BjoernKW]

For reference:

https://developer.apple.com/documentation/exposurenotification/enerrordomain
https://developer.apple.com/documentation/exposurenotification/enerror/code

This is the error code in question (5), which admittedly is not particularly helpful on its own ("Operation is not supported."): https://developer.apple.com/documentation/exposurenotification/enerror/code/unsupported

[airlenbauer]

I have the same issue. For a couple of days now.
Operation not supported us triggered by iOS usually when transforming data as in Data serialization and deserialization. ( i.e. Data to Codable struct) I haven’t worked with the Exposure Framework but Apple’s naming is quite consistent. These are not easy to debug though
Edit: Upon further thinking and checking my exposure logs in settings (which Corona Warn did 0 times). I may also be a read/write issue in i.e. saving an entity into CoreData IIRC correctly an “Operation not supported” May be thrown in such situation as well.

[FarahElI]

I have the same issue. I have an iPhone 11. The error appeared a couple of days ago. I deleted and installed the app again and checked the settings but nothing fixed it. My phone is unmanaged.

[AnkeHildebrandt]

Same issue. We have two phones in the household, installed the app around the same time. One has the error, one does not. One is 6s (working fine) one 7 (not working), both running 13.5.1. Tried to switch „Location Based Alerts“ on, as indicated by MisterRios did not work for me. Installed June 16, stopped working June 22.
Thanks for looking into this.

[avknobloch]

Bei mir ist der Fehler auch seit einigen Tagen und ich hoffe, dass Ihr es sehr bald löst. Hier meine Daten:

Modell iPhone SE (MLXP2DN/A)
Software iOS 13.5.1 (17F80)
Netzwerk: Telekom
Modem Firmware 9.60.01

Es geht um Corona, diese App ist wichtig. Wir fühlen uns unsicher und sehen den nächsten Lockdown vor uns. Der Technikstandort Deutschland blamiert sich.

[PITZH]

Ich habe die App seit dem ersten Tag in Benutzung - iPhone 7 Plus, private, unmanaged, 13.5.1. Risiko täglich aktualisiert.

Lief einwandfrei bis Mittwoch 24.6.2020 11:55. Da hatte ich die Risiko-Aktualisierung manuell in der App gestartet während ich eine schlechte Internet-Verbindung (Edge) hatte. Seitdem bekomme ich die Fehlermeldung.

Nach etwa einem Tag verschwand der Aktualisierungs-Knopf - die App meldet oben Risiko-Ermittlung aktiv, aber weiter unten erscheint der Knopf Risiko-Ermittlung einschalten - so wie auf dem Screen von ST-KW gezeigt. Da ist definitiv eine Inkonsistenz die die App kontrollieren können sollte.

Wenn ich die App heute normal starte kommt die Meldung 2 mal hintereinander. Wenn ich die App neustarte kommt sie 3 mal.

Wenn ich das iPhone neu starte und direkt nach dem Start die App starte, zeigt die App "Unbekanntes Risiko". Da scheint nach dem iPhone Start noch etwas zu fehlen. Dann App neu starten, dann Fehler wie oben beschrieben - 3 malige Meldung "Etwas ist schief gelaufen"

Ich habe die App nicht neu installiert da sonst meine Daten von Anfang an verloren gingen.

Update 30.06.2020 - reinstalled app 28.6.2020 - error still popping up. Exposure logging active, but risk status remains unknown as logging is not turned on long enough (which is not true).

[Stefie]

I‘m getting the same error since a couple of days, iPhone 11 on 13.5.1 and a re-install didn‘t help.

I just noticed that it goes away once I‘m in flight mode and comes right back when I re-enable mobile data or wifi. So it might have something to do with the authentification to download/ upload additional data that is needed by the app to calculate the exposures?

[Kljcjbjj]

Same error with iPhone 11 and iOS 13.5.1

The phone is in Austria a lot (working there).

[tkowark]

Thank you all again for providing us with details on this error. We're in close contact with Apple to narrow down this issue and find a solution.

Please continue to share interesting details, such as country switching, disabled iCloud Services, non-standard network configurations, etc. with us to have further input for these discussions. But please, don't upload further Screenshots of the Error message. It makes navigating the thread rather tough.

For all users that are concerned about losing their contact data by re-installing the app: This is not the case. Only explicitly deleting the data through Settings -> Privacy -> Health -> Covid-19 Exposure Logging -> Delete Exposure Log removes the contact events. The number of active days in the app is a different matter (#794 ). So, this is always worth a shot.

[christianbrb]

After reinstall on Friday the issue did not occur any more. I also had a bad internet before it happened.

Is it possible, that the data from the cwa-server isn’t downloaded and/or stored completely, this faulty or incomplete data is submitted to the ExposureNotification API and there it is throwing an error due to the faulty serialization (see https://github.com/corona-warn-app/cwa-app-ios/issues/766#issuecomment-650551640 from @airlenbauer).

[TShael]

Hi All, on my iPhone 8 everything is fine and under Setttings\Corona-Warn I can go to the bottom (blue text) to see the Covid-19 Kontaktprotokoll - after authentication I see a log of my contacts with timestamp: On my sons iPhone SE, there is not a single entry. He has this weird „Error 5“. I suspect, that there is not a small number out there with the App running - but with no effect, because it is virtually disabled. On my company phone (iPhone SE, managed) I realized, that the App also disables all contact checking silently once the powersaving mode is on. I had accidentially turned it on (76% battery) and wondered why the App showed some kind of disabled state (red WLAN on this comic picture of the contact check). After disabling power saving and restarting the App all was fine. Different topic, but interesting to know. Cheers, Peter Von meinem iPhone gesendet
…

I have the Error5 too. On an IPhone 6S, unmanaged, Software version 13.5.1
I read the post above, checked my contact log and realized that it’s empty, too. This is impossible if the app is working correctly, since my husband uses the app and at least his phone should be listed. His Iphone 8 has contacts listed and he didn’t get the error message.

Is it possible the error is linked to a problem with the contact log? It seemed to work fine the first days, but around the time when the first infections were entered for checking, the errors began. Maybe it’s caused when the app tries to compare the infections with the contact log and cannot find it?

[wjp-cs]

I removed other apps from my iPhone: radio.de, the soundtouch app from Bose and an old chess app.

I received error messages for about one more day. Then the corona warn app started working again.

[Revangelis]

I have the same error, deleted and reinstalled at least 5 times, iOs version is 13.5.1, phone is iPhone XR.

I have switched my app store country once after installing, then switched back to germany, I thought maybe that might have caused the problem but I have been in the german app store for 5 days and it still doesnt work after reinstalls.

[ReinholdL]

Just wanted to add my report to the list. I have the same error (iPhone SE, iOS 1.35). I had installed the corona app already on the day of its release, first worked all right, but I have ENErrorDomain-Fehler 5 since 23.June. I am from a Covid risk group, so I really hope the bug fix goes fast. I think you should add in your tips at https://github.com/corona-warn-app/cwa-app-ios/issues/766 that checking background refresh doesn't work in many cases. It is a bit annoying/frustrating that now there are quite some newspaper tips to fix the error, by using your above tips (but therefore not saying that they might only help in those cases, where users didn't activate background refresh, which then sounds as if it the problem is in all cases the user). I have checked everything time and again, have deleted quite some other apps, have transferred all photos on iCloud (despite not having had any memory problem) etc. etc. Only thing I haven't tried so far is to delete MY certificates for eduroam (hope that's not needed). I also have an inactive VPN profile, but don't think it's that. I understand that it must be Apple's bug, but the more often you contact them from GitHub, the better. (the official government hotline for Covid which I phoned quite some days ago also didn't know a solution). Many thanks!

[sascha-friederich]

I had the same error:
Iphone 11, IOS: 13.5.1

I could solve it, the following way:
in the settings (Allgemein->Info->Zertifikatsvertrauenseinstellungen), I found an self installed root-certificate installed (from Allianz Group, guess I had a project there in the past) - i disabled this certificate and since then, the corona-app is working again...
to reproduce the error i enabled the certificate, but the corona app is still working... perhaps other users had certificates themselves and try to disable this (once)

(does someone know how to uninstall these certificates, i dont need this anymore)

[ReinholdL]

Thank you! I checked your hint: all certificates were inactivate (except for the telecom one which I guess I need for phoning) In addition I also deleted my eduroam settings. Didn’t make a difference though, unfortunately.

Am 29.06.2020 um 15:47 schrieb sascha-friederich [e-mail]:

I had the same error:
Iphone 11, IOS: 13.5.1

I could solve it, the following way:
in the settings (Allgemein->Info->Zertifikatsvertrauenseinstellungen), I found an self installed root-certificate installed (from Allianz Group, guess I had a project there in the past) - i disabled this certificate and since then, the corona-app is working again...
to reproduce the error i enabled the certificate, but the corona app is still working... perhaps other users had certificates themselves and try to disable this (once)

(does someone know how to uninstall these certificates, i dont need this anymore)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-ios/issues/766#issuecomment-651132013, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQDUWRAV4VHBEBDL5T2NLBTRZCLN3ANCNFSM4OGS4E7A.

[kaisemarmuc]

I had the same error:
Iphone 11, IOS: 13.5.1

I could solve it, the following way:
in the settings (Allgemein->Info->Zertifikatsvertrauenseinstellungen), I found an self installed root-certificate installed (from Allianz Group, guess I had a project there in the past) - i disabled this certificate and since then, the corona-app is working again...
to reproduce the error i enabled the certificate, but the corona app is still working... perhaps other users had certificates themselves and try to disable this (once)

(does someone know how to uninstall these certificates, i dont need this anymore)

I also have such a certificate installed, however, I can‘t deactivate it.

[Filirator]

@tkowark
Immer noch Fehler "Etwas ist schiefgelaufen"... - seit Tagen.

Trotz der Aussage ("we...find a solution") erscheint mir Computerlaien die Arbeit an einer Lösung wie Stochern im Nebel.

Gibt es keine Information von den Programmierer*innen?

[sascha-friederich]

i´m also a telekom customer, but dont have a telekom certificate - did you try to disable it, restart the corona-app and enable the certificate?

[ReinholdL]

Thanks, I saw that the telekom certificate was deactivated anyway. I also now deactivated all background refreshes for all apps except for the corona warn app, just to see whether it makes a difference. Doesn’t (even after a restart). I am giving up for today, but many thanks for the tips. Maybe the old iphoneSE just doesn’t work (despite 13.5.1 and apple statement that it should work

Am 29.06.2020 um 16:39 schrieb sascha-friederich [e-mail]:

i´m also a telekom customer, but dont have a telekom certificate - did you try to disable it, restart the corona-app and enable the certificate?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-ios/issues/766#issuecomment-651164565, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQDUWRHHDX2MWRUFJTLKE43RZCRS3ANCNFSM4OGS4E7A.

[christianbrb]

Sounds like this PR could be a workaround for the problem: https://github.com/corona-warn-app/cwa-app-ios/pull/536

My assumption is that somewhere in the DownloadedPackagesSQLLiteStore wrong data is getting stored due to errors downloading, transferring to in memory and storing the file.

At least in some cases where the reinstallation of the app fixes the problem.

CC @SebastianWild

[svona-ai]

Same issue here, iPhone XS with 13.5.1 unmanaged. Stopped working with this error about 2 days ago, realized it when traveling from Munich to Frankfurt (but may have stopped working before), had the last status update on 22 June. Deleted the app and reinstalled, still the same issue.

My app is working again since just now, without knowingly doing or changing something.

[ReinholdL]

Thank you for the information, congrats! Your news gave me some hope, so I directly checked my phone, but, hmm, mine still shows the error.. So then: Let’s hope for the best but expect the worst (not!)

Am 30.06.2020 um 16:13 schrieb svona-ai [e-mail]:

Same issue here, iPhone XS with 13.5.1 unmanaged. Stopped working with this error about 2 days ago, realized it when traveling from Munich to Frankfurt (but may have stopped working before), had the last status update on 22 June. Deleted the app and reinstalled, still the same issue.

My app is working again since just now, without knowingly doing or changing something.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-ios/issues/766#issuecomment-651818449, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQDUWRES4BH3LRUBREPJDMDRZHXJXANCNFSM4OGS4E7A.

[Hermann12]

Thank you for the information, congrats! Your news gave me some hope, so I directly checked my phone, but, hmm, mine still shows the error.. So then: Let’s hope for the best but expect the worst (not!)

Am 30.06.2020 um 16:13 schrieb svona-ai [e-mail]:

Same issue here, iPhone XS with 13.5.1 unmanaged. Stopped working with this error about 2 days ago, realized it when traveling from Munich to Frankfurt (but may have stopped working before), had the last status update on 22 June. Deleted the app and reinstalled, still the same issue.

My app is working again since just now, without knowingly doing or changing something.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-ios/issues/766#issuecomment-651818449, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQDUWRES4BH3LRUBREPJDMDRZHXJXANCNFSM4OGS4E7A.

Still no change. Deleted the app and install it again. Same error message appears, before set up is done. Two blinking message box with the error 5

-> Solved today, thanks!

[avknobloch]

Glückwunsch, Ihr habt das Problem gelöst, vielen Dank! Bei mir sind jetzt noch 4 Tage statt 10 Tage registriert und Basis für niedriges Risiko. Ab heute 0:20 wird es ohne Fehlermeldung angezeigt.

Vor vier Tagen hatte ich einen Reset des iPhones gemacht (Ausknopf 10sec). Sonst hatte ich keine aktiven Löschaktionen.

Euch alles Gute, bleibt gesund!!

[Filirator]

@avknobloch
<

Leider nein, neuer Tag, Fehler bleibt.

[christianbrb]

@thomasaugsten @SebastianWolf-SAP Is there any update from your internal analysis and talks with Apple? Do you expect this to be resolved with the latest release?

[ReinholdL]

Bei mir bleibt das Problem leider auch, trotz dieses Tipps, den ich auch ausprobiert habe (Ausschalten, ne Minute warten, neu starten). Hab auch Airdrop und Airplay ausgeschaltet (wg. Zugriff auf Bluetooth). Einziger Unterschied. Die Fehlermeldung flasht jetzt nicht dreimal, sondern nur noch zweimal auf (??)

Am 01.07.2020 um 07:53 schrieb Filirator [e-mail]:

@avknobloch https://github.com/avknobloch
<

Leider nein, neuer Tag, Fehler bleibt.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-ios/issues/766#issuecomment-652207539, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQDUWRC7MMSSKK6YC3ZLCXDRZLFORANCNFSM4OGS4E7A.

[PITZH]

Bei mir ist die Meldung seit heute morgen 6:05 weg. App meldet 2 von 14 Tagen aktiv - wenn keine Daten beim App löschen verloren gehen wie geschrieben sollten es ab heute eigentlich 14 aktive Tage sein.
Ob die App nun wirklich funktioniert ist schwierig zu beurteilen - wo ausser in der Übersicht kann man denn erkennen dass die App etwas tut, Daten entstehen etc.?

[stmTh]

We have two Iphone 8.
One of it had this error for about 10 days, app wasnt working no covid tracing in logs.

Today its working.

We deleted the tracing protocol and the whole app yesterday in the evening.
We reinstalled it this morning and now it seems to work since about ~1h.

[neb382]

interessting, i did all the same but my app isnt working. iphone 11

[ReinholdL]

PS: soon I’ll become a conspiracy theory follower (no, don’t worry ;-). But after my mail below, now (50 Min later), my app suddenly works, updated at 9:05 am, German time). Very mysterious. (Consolation: I have low risk status).

So I guess, one of the following, or the combination of it, might have done the job:

• closing all other applications,
• deactivating all other bluetooth-based services (such as air play, air drop)
• restarting the iphone (with a few minutes having the phone completely off),
• and then waiting patiently for about one hour.
  Fyi: I had never deleted the data in the app nor reinstalled the app.

To me it looks a bit like a working memory issue, at least for my old iPhoneSE from ?2016

Many thanks to all who gave tips here. Great community! And I do hope that the issues of the others will also disappear in the air soon.

Am 01.07.2020 um 08:13 schrieb Reinhold Leinfelder [e-mail]:

Bei mir bleibt das Problem leider auch, trotz dieses Tipps, den ich auch ausprobiert habe (Ausschalten, ne Minute warten, neu starten). Hab auch Airdrop und Airplay ausgeschaltet (wg. Zugriff auf Bluetooth). Einziger Unterschied. Die Fehlermeldung flasht jetzt nicht dreimal, sondern nur noch zweimal auf (??)

Am 01.07.2020 um 07:53 schrieb Filirator <[email protected] [e-mail]>:

@avknobloch https://github.com/avknobloch
<

Leider nein, neuer Tag, Fehler bleibt.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-ios/issues/766#issuecomment-652207539, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQDUWRC7MMSSKK6YC3ZLCXDRZLFORANCNFSM4OGS4E7A.

[SebDE]

I had the same error (started at 24.06.2020). I did not:

• restart the app
• restart the phone (iPhone X)
• restart bluetooth

Today at 06:23 the app was able to send the informations and now everything works like before. I hope this information is helpful to find the final reason for the issue.

Update: The App-Store update history shows that today a new version (1.0.3) was installed - could be possible that this was the fix ...

[djaegerDe]

Had the Error as reported here in the thread above.
I had uninstalled the app 4 days ago, deleted the contact log and reinstalled it, but the error was still there. Otherwise I have not made any other known changes.
Turned my iPhone off today in the morning, waited about 60 Minutes before turning it on again
I have started the corona App and the error message is gone, the app seems to work as expected.
I have not updated the app to version 1.0.3 before.

[ReinholdL]

Oh, I didn’t notice that now there is an update of the app. Has anybody installed it and got problems again? Am a bit worried whether to use the update. Just solved the earlier problem with the old version and really don’t want Error 5 back again ;-)

Am 01.07.2020 um 10:31 schrieb djaegerDe [e-mail]:

Had the Error as reported here in the thread above.
Turned my iPhone off today in the morning, waited about 60 Minutes before turning it on again. Otherwise I have not made any other known changes.
I have started the corona App and the error message is gone, the app seems to work as expected.
I have not updated the app to version 1.0.3 before.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-ios/issues/766#issuecomment-652275577, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQDUWRAAVKNDCZHE7U3HJ5LRZLX4ZANCNFSM4OGS4E7A.

[Launethil]

I installed the 1.0.3 update this morning, which didn't fix the issue for me. Fortunately however, it disappeared between 9 and 10 AM. Still not sure what fixed it (I did log out of and back into my iCloud account on my Macbook), but the app is currently working as expected (the COVID-19 Exposure Logging now also shows Exposure Checks, which it didn't previously).

[jantenne]

I have the 1.0.3 update also. The error is still there, but the view is slightly different as it shows now "Unbekanntes Risiko" and did not longer show "Risiko-Ermittlung einschalten" as it was before even if the setting was "on". I did also deleted the protocol and restarted the phone.

[AnkeHildebrandt]

Same issue. We have two phones in the household, installed the app around the same time. One has the error, one does not. One is 6s (working fine) one 7 (not working), both running 13.5.1. Tried to switch „Location Based Alerts“ on, as indicated by MisterRios did not work for me. Installed June 16, stopped working June 22.
Thanks for looking into this.

Update: It worked today at 11 am. Had not yet updated. I tried several times per day since I posted here. Kontaktprotokoll etc. all with data. Hope this helps. Curious what will happen tomorrow ..

[ReinholdL]

Thank you all, it’s really strange. I now also updated to app version 1.03 , Error5 didn’t come back, good. was about to believe, that they optimized the server, since many apparently got rid of Fehler5 today between 9 and 11 am. However, doesn’t match with you. Remains mysterious.

Am 01.07.2020 um 10:45 schrieb jantenne [e-mail]:

I have the 1.0.3 update also. The error is still there, but the view is slightly different as it shows now "Unbekanntes Risiko" and did not longer show "Risiko-Ermittlung einschalten" as it was before even if the setting was "on". I did also deleted the protocol and restarted the phone.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-ios/issues/766#issuecomment-652282835, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQDUWRH7HM7DPFHYSJIRI63RZLZR5ANCNFSM4OGS4E7A.

[cityinsouth]

Die App funktioniert bei mir seit 23.06.20 nicht mehr. Löschen und neu installieren hat keinen Erfolg gebracht. Airdrop und Airplay sind ausgeschaltet. Auschalten und wieder hochfahren bringt auch keine Lösung. Mobile Daten sind aktiviert. Iphone 7, Softwareversion 13.51. Beim öffnen der App erscheint die Fehlermeldung dreimal kurz hintereinander. Bei meinem Mann gleiches Iphone mit gleicher Softwareversion und gleichen Einstellungen (zumindest unser Eindruck) funktioniert die App ohne Probleme.

[kaisemarmuc]

Very strange: I did absolutely nothing, but it works again since just now. It didn‘t work in the morning. However, I lost one week - it says, it is active for three days now. It seems like it paused for one week...

[zerbes]

The miracle also happend to me: i checked several times today and suddendly the errormessage does not show up anymore

[ideasondesign]

Did an app reset, cleared the exposure log, updated, restarted the iphone. And still the same problem.

Even if you can’t replicate the problem on your side or collect data, this is of such paramount importance, that I would expect you to collect devices that display the error to further collect information.

[TShael]

According to the App Store there was an Update 22 hours ago - and the error is gone!
The app says active for 3 days. Looks like it didn’t register the time with the error.

Still not sure if it works as intended. I don’t seem to have a list with contact IDs, though it should at least register my husband’s mobile. And there were contact checks, but nothing to compare them with. Please see the attached screenshot. Is this working correctly???

[ellipticsun]

I had this error (5) for a week and yesterday it changed to error 13. I tried upgrading to 1.0.3 but it made no difference unfortunately.

[auxua]

For me the update to the new version fixed the error (and set back the active days to a smaller value)

Thanks for the fix 😀

[airlenbauer]

The update sadly didn’t work for me as well as the other tricks. Restart, reinstall, clear exposure log etc
iPhone 8
iOS 13.5.1

[romyrow]

The update sadly didn’t work for me as well as the other tricks. Restart, reinstall, clear exposure log etc
iPhone 8
iOS 13.5.1

exact same here. 😕

[nrd-tx]

For the first time since days the app is working now (i think since a few hours) without the "Fehler 5" failure. Today afternoon there was this "this location is not supportet..." pop up. I then checked my contact protocoll and for the first time (dont know if for the first time ever or just since app stopped working) there were some timestamps. (all the same time 8:50)

[christianbrb]

@thomasaugsten @SebastianWolf-SAP Is there any update from your internal analysis and talks with Apple? Do you expect this to be resolved with the latest release?

I know all of you are really working hard and late. Nevertheless, could somebody give us a brief update? There seem to be a lot of iPhones affected

CC @inf2381

[ReinholdL]

Arrgh, as reported here, after lots of fiddling I got rid of Error 5 - like many other - two days ago (still under vers. 1.01). Then updated to 1.02, and app remained working. Now I am checking, and the problem is back, flashing up twice saying „etwas ist schiefgelaufen“ . So no risk actualization since yesterday morning. However now ENErrorDomain-Fehler 5 (as it was before) has „miraculously“ transformed to ENEDomain-Fehler 11 ?????
I am about to giving up and delete the entire app.

Am 02.07.2020 um 21:06 schrieb christianbrb [e-mail]:

@thomasaugsten https://github.com/thomasaugsten @SebastianWolf-SAP https://github.com/SebastianWolf-SAP Is there any update from your internal analysis and talks with Apple? Do you expect this to be resolved with the latest release?

I know all of you are really working hard and late. Nevertheless, could somebody give us a brief update? There seem to be a lot of iPhones affected

CC @inf2381 https://github.com/inf2381
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/corona-warn-app/cwa-app-ios/issues/766#issuecomment-653174608, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQDUWRAID4JKYLDPG4GFLTTRZTLBVANCNFSM4OGS4E7A.

[ReinholdL]

Correction of last posting (confused app versions), here correct, sorry for that:

Arrgh, as reported here, after lots of fiddling I got rid of Error 5 - like many other - two days ago (still under vers. 1.02). Then updated to 1.03, and app remained working. Now I am checking, and the problem is back, flashing up twice saying „etwas ist schiefgelaufen“ . So no risk actualization since yesterday morning. However now ENErrorDomain-Fehler 5 (as it was before) has „miraculously“ transformed to ENEDomain-Fehler 11 ?????
I am about to giving up and delete the entire app.

PS: I had the phone in flight modus (including bluetooth off) over night, which earlier had caused no problem. So I don’t think it was that. And now I have restarted the iphone (with a few minutes letting it completely off), didn’t make a difference. Error 11 still acting up.

Am 03.07.2020 um 11:26 schrieb Reinhold Leinfelder [e-mail]:

Arrgh, as reported here, after lots of fiddling I got rid of Error 5 - like many other - two days ago (still under vers. 1.01). Then updated to 1.02, and app remained working. Now I am checking, and the problem is back, flashing up twice saying „etwas ist schiefgelaufen“ . So no risk actualization since yesterday morning. However now ENErrorDomain-Fehler 5 (as it was before) has „miraculously“ transformed to ENEDomain-Fehler 11 ?????
I am about to giving up and delete the entire app.

[tkowark]

In the meantime, we updated our FAQ with recent information about the common ENF errors: https://www.coronawarn.app/de/faq/#ENError5

In short, Error 5 should mostly be gone for everybody either now or in the near future. Please only comment further on this issue, if you are still experiencing error 5. Error 11 and 13 are tracked in #759

If error 5 does not occur anymore throughout the weekend, we'll close this issue on Monday.

[robhuen]

Right now, I still have a phone (current version of iOS and app) with ENError 5.

I tried restarting the phone and deleting and reinstalling the app without effect (except for loosing the active days). I will watch if it changes throughout the weekend.

[christianbrb]

@tkowark Thanks for the update :)

[jakomar-tech]

When the error occurs, I see that the app is trying to connect to gateway.icloud.com. What fails. Hope that helps

[robhuen]

Just installed the update to 1.0.4: Error is still there.

[phaenoo]

iPhone and App have the latest version (the App has version 1.0.4). However, the error message still appears.

[Hubersan]

To share some good news: On my son‘s iPhone (SE, unmanaged) with the latest Corona Warn App 1.0.4 (0) the error-5 is now apparently gone. (:-)
Thanks to all hard working folks!

Von meinem iPhone gesendet

Am 05.07.2020 um 11:05 schrieb Roman Schulz [e-mail]:


Still experiencing this issue it with iOS 14 Dev Beta

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[robhuen]

So far the error still occurs. Just waiting as mentioned in the FAQ did not help (yet). Please do not close the issue (yet).

[ehonk]

With Version 1.0.4 still the same error on my iPhone 7 (iOS 13.5.1).

[dig8l]

iPhone X. iOS 13.5.1. App version 1.0.4 (0). Error all the time. Still. Even now. Not good ... Fix please?

[sinky]

iPhone Xr. iOS 13.5.1. App version 1.0.4

Fehler tritt hier bei Neuinstallation der App auf. (wg. weiterhin 13/14 Tagen-Fehler)

Einmal im Screen "Falls Sie Corona-positiv getestet werden ..."
und einmal im Hauptbildschirm nach abschließen des Einrichtungsassistenten.

[robhuen]

For the records: my ENError 5 switched to ENError 13 two days ago without me changing anything. Yesterday also ENError 13 was gone and the app now seems to work as intended.

[tocotronaut]

This bug should have been adressed with release of iOS 13.6 yesterday.

What about Closing this issue?

[SebastianWolf-SAP]

According to the feedback which we have been receiving via the App Store, the Error 5 has been gone already for quite some time. As 13.6 was also released, we will close this issue for now. Please report back in case the error comes up again.

Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team