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

[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.

[Osaltuk90]

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 notifications@github.com:

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 notifications@github.com:

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 notifications@github.com:

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 notifications@github.com:

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 <<Glückwunsch, Ihr habt das Problem gelöst, vielen Dank!

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 notifications@github.com:

@avknobloch https://github.com/avknobloch <<Glückwunsch, Ihr habt das Problem gelöst, vielen Dank!

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 rleinfelder@googlemail.com:

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 <notifications@github.com mailto:notifications@github.com>:

@avknobloch https://github.com/avknobloch <<Glückwunsch, Ihr habt das Problem gelöst, vielen Dank!

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 notifications@github.com:

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 notifications@github.com:

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