ENErrorDomain-Fehler 11/13

[chk-code]

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 twice, fast after each other.

Expected behaviour

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

Steps to reproduce the issue

First time error code was 11

Now, it says error code 13

1. Open the app
2. Wait

(7/14 Days active. Last Update of the Status: Vorgestern)

Technical details

• iOS Version: 13.5.1
• Device: iPhone XR

---

Internal Tracking ID: EXPOSUREAPP-1911

[chk-code]

App was closed and hard closed a couple of times, But no difference in the behavior.

I remember that some days ago I received a system notification from the Tracking protocol that something went wrong.

Seems like this error comes from the Tracking Protocol?

[pstadt]

Same problem here (ENErrorDomain-Fehler 11), iPhone SE, iOS 13.5.1

Disappeared after restart of phone.

[felixoi]

I've the same issue.
iPhone XS Max, iOS 13.5.1

[chk-code]

Same problem here (ENErrorDomain-Fehler 11), iPhone SE, iOS 13.5.1

Disappeared after restart of phone.

Restart didn’t fixed it for me.

[haosap]

Hi @chk-code ,
Thanks for your report. We will try to reproduce this issue.
Meanwhile, copied directly from the header file of EN Framework.

 ENErrorCodeInternal = 11, /// Internal error. This indicates a bug in this framework. 

It seems an issue of the framework.
We'll also align with Apple.

[tens0rfl0w]

This error occurs when the API gets called to often in an internal defined time frame. So there has to be a breakpoint where the hook-up function gets into a loop calling the framework or a wrong condition leading to multiple calls. (This is related to Error code 13/rate limited)

It makes sense that the error occurred now, and not earlier, because today was the first time the app actually called the API to check matching key identifiers.

@chk-code Did the app accessed the framework? You can check that under Settings app->Privacy->Health->“COVID-19 Exposure Logging“. Under „Active apps“ there is a grey text where you can see the number of times the framework was accessed. Under „Exposure Checks“ you can also get a JSON output of the check. So you can see if the access was successful.

[chk-code]

@tens0rfl0w Seems like it didn’t access the api?

Still getting the error message, after some hours

[tens0rfl0w]

@chk-code Ok, thank you! You are right, there was no successful access to the framework from the app. Seems like it is an internal framework bug like @haosap already pointed out. Would be interesting to know if error 13/„rate limited“ occurred because the app run into internal error 11 and retried connecting to the API to often, or if error 13 happened first and after that the API broke.

[haosap]

Hi @tens0rfl0w @chk-code ,
We have already addressed this to Apple and are waiting for the response from Apple.
Thanks for reporting this issue. cc @ChristianKienle

[mf71]

Same error for me. @tens0rfl0w for me it's only error 11. I did get it first a few minutes ago. I did install on day one and didn't start/restart the app frequently. IphonXs. Btw I am also getting the "Region für die Kontaktmitteilung.." message since time of Installation.

[ForlornWongraven]

Same issue as @chk-code reported appeared on my iPhone 11 after a restart.

[toddy]

I have also the error 11/13. Yesterday it works like the other days before without this issue.

[Siska2]

Same here : / on my IPhone 11 Pro

[thomasaugsten]

Did somebody get this error with 13.6 Beta2?

[dnuc]

I also have error 13 since yesterday. It worked the days before without any issue. Iphone XR - iOS 13.5.1
Restart does not help.

[npasslick]

Same error for me (since 23.06.2020). Restart did not fix the issue for me.

Although the app itself regularly indicated a refresh in the risk pane during the last nine days of tracing, the COVID-19 protocol of iOS seems never to have been accessed successfully (iOS settings indicates zero accesses to the protocol, checked daily).

Additionally, an iOS warning "Not enough storage space for COVID-19 tracing" popped up once, although plenty of space is available.

Model: iPhone 6S
OS: iOS 13.5.1
Tracing: 9/14 days
Last update: 23.06.2020 15:50

[BettinaPfeifer]

same here, first domain-error 11 occured, now domain-error 13,
iPhone 7, iOS 13.5.1,
tracing 9/14 days,
Aktualisiert: vorgestern
The "not enough storage space" also showed up yesterday, but vast amount of storage available.

EDIT: as others mentioned before, later that day, this error disappeared by itself. :-)

[kraftzwerg]

I have excactly the same Error "ENErrorDomain-Fehler 13"
aktualisiert: vorgestern
Tracing 7/14 Days (that was two days ago, and does not count higher anymore)
Iphone 8. IOS 13.5.1
Restarting the IPhone did not help.

For me after two days of struggeling i found the best solution for me:
Just uninstall the app and wear a mask.

Its a shame

[chk-code]

Somehow, today the problem solved itself for me. I have an updated status from 8am.

Also, I can see that the Framework had 2 successful calls (privacy-health-COVID 19)

Seems like something happened in the background or the deadlock recovered?

Cc: @haosap @tens0rfl0w

[pavshr]

Hello, guys

I work on the Danish app. We see this error (ErrorCode 11) as well. Based on our observation, this issue occurs when the phone submits the zips files with the keys to the EN API for detecting exposures. Then it returns this error (ErrorCode 11) from EN API, if we go to Settings and check COVID-19 logging page there are no exposure checks on the phone, on which we are able to reproduce the problem. Basically, it means that the error is thrown when doing exposure detection and leads to termination of the exposure detection process.

We are now trying to update the device to 13.6 beta and see if the error remains there.

[thomasaugsten]

Can you confirm that the errors are gone after one day waiting?

[Siska2]

It is solved for me too!! I reinstalled the app several times. Today it seems to be working. iOS 13.5.1, iPhone 11 Pro

[toddy]

Can you confirm that the errors are gone after one day waiting?

Is it necessary to reinstall the app like Siska2 referred?

[pavshr]

If the error 11 is somehow related to error 13 (would be great to get an insight on that from Apple), which I understand is the case for the German app, then it should help to wait one day. On iOS there is a limit on how many key files you are allowed to submit to EN API during the day. This limit is set to 15 files (src). In other words, if you have already submitted 15 files today, then you need to wait one day to call detectExposures again without error being thrown. On the other hand, if you try to submit more than 15 files during the day, we would expect error 13 to be thrown, but for some reason error 11 is thrown too in your case.

[thomasaugsten]

Error 13 is the rate limit of 15 files. Error 11 is an internal error of the framework.
The app are retrying the risk analysis at every start until it reached the rate limit error 13.
After one day all errors are gone.

[Anguel]

To be honest, I have not seen any app producing so many "something went wrong" errors in the last years as the German Corona-Warning-App, both on iOS and Android. I am sure this thing does not do its job properly (besides known counting problems), as no warning is shown at all until you open the app. Good job, SAP and Telekom!

[kevin-kraus]

Version: 1.0.4
Device: iPhone X (MQAG2ZD/A)
Screenshot:

App konnte seit 02.07.2020 keine neuen Daten abrufen.

[ReinholdL]

guess you updated to app v.1.0.4 and then this error 13 appeared. Waiting for max 24 hrs solves the problem in most cases, so hope it also works in your case. See also https://www.coronawarn.app/en/faq/ <https://www.coronawarn.app/en/faq/>

…

Am 08.07.2020 um 13:32 schrieb Kevin ***@***.***>: Version: 1.0.4 Device: iPhone X (MQAG2ZD/A) Screenshot: <https://user-images.githubusercontent.com/36297312/86913686-4a205000-c11f-11ea-92bf-dfc6b750d67d.png> App konnte seit 02.07.2020 keine neuen Daten abrufen. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#759 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQDUWRDMOBNX5U3VS5U745DR2RKL3ANCNFSM4OGKFJ4A>.

[kevin-kraus]

guess you updated to app v.1.0.4 and then this error 13 appeared. Waiting for max 24 hrs solves the problem in most cases, so hope it also works in your case.
See also https://www.coronawarn.app/en/faq/ https://www.coronawarn.app/en/faq/

Am 08.07.2020 um 13:32 schrieb Kevin notifications@github.com:

Version: 1.0.4
Device: iPhone X (MQAG2ZD/A)
Screenshot: https://user-images.githubusercontent.com/36297312/86913686-4a205000-c11f-11ea-92bf-dfc6b750d67d.png
App konnte seit 02.07.2020 keine neuen Daten abrufen.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #759 (comment), or unsubscribe https://github.com/notifications/unsubscribe-auth/AQDUWRDMOBNX5U3VS5U745DR2RKL3ANCNFSM4OGKFJ4A.

Nope, app got automatically updated 3 days ago. And the app tells me that it hasn’t got updated in the last 6 days. So I do not think the Update has something to do with the error.

[fischerwulf]

I'm experiencing this issue (Error 13) on an iPhone 6s plus with iOs 13.5.1 and cwa version 1.0.4.

Looking at the exposure settings, this seems to stem from the app hitting the rate limit for exposure requests. (Note 20 times in last 24 hrs)

Looking at the log of exposure checks the app seems to be resubmitting old keys for exposure checks:

Hunting around in there I found exposure checks on subsequent days with the same keycount and hash:

Best guess what's happening (I haven't looked at your code): The app is resubmitting old keys instead of focusing on newer ones.

I hope this helps. If I can provide further info, let me know.

[Petk12]

I have it on the current version 1.0.4 too, IPhone8. Reboot did not help.

[tugbabodrumlu]

Hi, I have the same problem as well and nothing helps. I also see that the app checked the log 20 times over the last 24 hours. Could it be deterministic? I'm on iOS 13.5.1

[spinscale]

I also get the 11 error, on top of that my exposure logging is deactivated, and when I activate that I get this error (plus when opening the app). I also got an error that the storage for storing is full, albeit more than than 60gb are free on my phone -not sure which storage is referred to. Would deleting the stored data be worth a try?

[tugbabodrumlu]

@spinscale Did you check how many log checks do you have? @fischerwulf 's explanation makes a lot of sense to me so I wonder if anybody has a working app after 20 log checks.

[kevin-kraus]

@spinscale Did you check how many log checks do you have? @fischerwulf 's explanation makes a lot of sense to me so I wonder if anybody has a working app after 20 log checks.

I actually can remember that yesterday I also had 20 Checks. App not working and errors etc. Today after your comment I looked, got 14 checks. App works now like a charm so probably the cause for this behavior is exactly what you said and it only happens >=20 checks.

[fischerwulf]

What I don't understand is why it's necessary to resubmit old keys. These keys are from past days and once they have been submitted to the server no new contact codes would be generated from these. There is no extra information to be gained from rechecking these keys more than once. Hence it should suffice to check the diff between the currently available and already checked keys. Therefore only one exposure check per day should suffice.
I'm guessing the risk score is calculated from scratch each time and all keys stored on the phone are submitted in the batches that they were received from the server. This then runs into the rate limit of max 20 checks per 24 hrs if too many batches are in the local db.

However this reasoning is based on a rudimentary understanding of the framework and how the app works. (Again, I haven't looked at the code and am happy to be proven wrong and know that there might be considerations which I'm not aware of)

[spinscale]

@tugbabodrumlu my last exposure checks are from four days ago and I do not see 20 checks for that day, but only 12, if that helps anything.

[tugbabodrumlu]

@spinscale It is hard to speculate before checking the code as @fischerwulf also commented, but I asked around and 3 people who had more than 20 log checks had exactly the same problem.

[tugbabodrumlu]

@kevin-kraus This morning I also got 14 checks and app works normally.

[kevin-kraus]

@tugbabodrumlu yes same over here. But now another problem shows up: the App is constantly installed and running since release but still I only get 13/14 days displayed.

[dsouzajj]

• It's been more than 14 days and the app still shows 13/14.

• It also says there's not enough storage although my phone has 34 GB free space. This message never appeared again.

[tkowark]

Issue 11 should be fixed with iOS 13.6 and better explanatory texts were introduced with app version 1.0.5
If you experience these issues again on the latest app and iOS versions, please open a new, dedicated issue for that.

Thank you all for your input!

[chk-code]

Issue 11 should be fixed with iOS 13.6 and better explanatory texts were introduced with app version 1.0.5

If you experience these issues again on the latest app and iOS versions, please open a new, dedicated issue for that.

Thank you all for your input!

Still open issue
Fehler 11

[tkowark]

Since the Twitter user was not really on "Neuste and Neuste", let's close this issue as discussed before. If anybody has the latest app and iOS 13.6 (or higher), please open a new issue.

[thomasaugsten]

@brandtaucher Hi kannst du mich direkt anschreiben mit dem Fehler und Version die du verwendest?