ENErrorDomain-Fehler 5

[christianneu]

Avoid duplicates

• Bug is not mentioned in the FAQ
• 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

[FabianClemenz]

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?

[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 ***@***.***>: @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 <#766 (comment)>, 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 ***@***.***>: 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 ***@***.***>:  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