-
Notifications
You must be signed in to change notification settings - Fork 288
ENErrorDomain-Fehler 5 #766
Comments
Error code 5 is "Operation is not supported." Do you have special conditions on you phone like profiles, proxy using a second Corona App? |
Same error here. Started today. iOS 13.5.1. Last Update 22.06.2020 22:00 |
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 |
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 |
Hi @HoSch-193 , |
Hi @tkopton, |
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. |
see comment above |
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. |
Same with me. Unmanaged. iPhone X. 13.5.1. app worked until 23.6. device is not managed. |
Same problem on iPhone 8 Plus, iOS 13.5.1. Last update 22.06.2020. Private device without special profiles. |
Same here for an unmanaged iPhone SE (first generation). |
Same error here, iPhone X, iOS 13.5.1, no MDM, VPN or whatsoever |
Same error iPhone 7, private, 13.5.1 |
Same error on my Dads iPhone
|
Same error here, it |
This is the only thread I find. I found one tweet from another person to it^^ |
After posting here it worked the first time for 48 hours. It’s back working^^ |
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. |
Hi @flixflax , |
I tried that yesterday, same problem right away. |
Same with me. I use iOS13.5.1 on iPhone X, no MDM, no VPN. I deleted the app and reinstalled it. Same issue... |
Dear app users, |
Have the same issue. Private unmanaged phone. |
Same error message on iPhone 6s. It worked before, now it doesn't update since 23.6. |
Can the app save error logs and report them to your server? Is there a way one can enable this? |
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. |
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... |
The miracle also happend to me: i checked several times today and suddendly the errormessage does not show up anymore |
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. |
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. |
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 😀 |
The update sadly didn’t work for me as well as the other tricks. Restart, reinstall, clear exposure log etc |
exact same here. 😕 |
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) |
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 |
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>.
|
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.
|
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. |
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. |
@tkowark Thanks for the update :) |
When the error occurs, I see that the app is trying to connect to gateway.icloud.com. What fails. Hope that helps |
Just installed the update to 1.0.4: Error is still there. |
iPhone and App have the latest version (the App has version 1.0.4). However, the error message still appears. |
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.
|
So far the error still occurs. Just waiting as mentioned in the FAQ did not help (yet). Please do not close the issue (yet). |
With Version 1.0.4 still the same error on my iPhone 7 (iOS 13.5.1). |
iPhone X. iOS 13.5.1. App version 1.0.4 (0). Error all the time. Still. Even now. Not good ... Fix please? |
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 ..." |
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. |
This bug should have been adressed with release of iOS 13.6 yesterday. What about Closing this issue? |
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, |
Avoid duplicates
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
Technical details
The text was updated successfully, but these errors were encountered: