Cwa-app-ios: Error 13 after upgrading to CWA 1.9.1 and opening the app

[ouboub]

Error 13 after upgrading to CWA 1.9.1 and opening the app

See this FAQ entry:

• English https://www.coronawarn.app/en/faq/#ENError13
• German https://www.coronawarn.app/de/faq/#ENError13

If you updated to Corona-Warn-App version 1.9.1., some users may receive the following error message:

• German error message: "Fehler 13: Ihre Risiko-Ermittlung für den heutigen Tag wurde bereits durchgeführt. Bitte versuchen Sie es in 24 Stunden erneut."

• English error message: "Error 13: Your exposure logging for today has already been carried out. Please try again in 24 hours."

The Corona-Warn-App is functioning correctly despite this message. If you have any other problems in this context, you can describe your issue in detail in this thread.

Corona-Warn-App Open Source Team

---

ORIGINAL POST BY THE AUTHOR

Hi
I upgraded yesterday. Today, in the morning I opened the app, and an error message up, that made little sense,
the check was done correctly, though.
The screenshot is attached
regards
Uwe Brauer

---

Internal Tracking ID: EXPOSUREAPP-4066
Internal Tracking ID: EXPOSUREAPP-4145
Internal Tracking ID: EXPOSUREAPP-4906

[Ein-Tim]

@ouboub
Did you use 1.7.1 before the update?

[dsarkar]

Hi @ouboub,

Thanks for reporting. However, you can ignore this message.

If you open the app for the first time after the update, a risk check is initiated immediately, regardless of whether or not a check has already been carried out. This means that in some cases users may receive this error message.

Reference: EXPOSUREAPP-4066

Best wishes, DS

---

Corona-Warn-App Open Source Team

[ouboub]

Hi @ouboub,

Thanks for reporting. However, you can ignore this message.

If you open the app for the first time after the update, a risk check is initiated immediately, regardless of whether or not a check has already been carried out. This means that in some cases users may receive this error message.

Reference: EXPOSUREAPP-4066

Best wishes, DS

Corona-Warn-App Open Source Team

Yes I thought, I could ignore it, but I also thought it is worth letting you know, because it might confuse other users

[ouboub]

@ouboub
Did you use 1.7.1 before the update?

I am pretty sure the answer is yes, but how I can I check it to be completely sure?

[dsarkar]

Thanks, we will update the FAQ https://www.coronawarn.app/de/faq/#ENError13 now.
And yes, we are very happy about any feedback. It tells us also, that we need to communicate more clearly and in a more timely manner.

---

Corona-Warn-App Open Source Team

[Ein-Tim]

@ouboub

I am pretty sure the answer is yes, but how I can I check it to be completely sure?

You can't... But since @dsarkar stated that this does not mean anything, it's not relevant anymore

[ouboub]

Thanks, we will update the FAQ https://www.coronawarn.app/de/faq/#ENError13 now.
And yes, we are very happy about any feedback. It tells us also, that we need to communicate more clearly and in a more timely manner.

Corona-Warn-App Open Source Team

thanks, but it also clearly shows, that it would be better to have more beta testers. Im telling you this also because I am beta tester in various Apple Apps.

[ellenkoenig]

I have a somewhat different behavior than the initial reporter. I get the same error, but the check doesn’t happen. So my risk status is „unknown“. I have not opened the app in a few days prior to upgrading. Of course, starting the risk check sync manually also fails.

[Ein-Tim]

@ellenkoenig

Wait, you can't manually start the risk check? What happens when you click the button? Does the error show up again?

[ellenkoenig]

@Ein-Tim yes, exactly

[Ein-Tim]

Okay...
@ellenkoenig
Did a restart from the App/your phone change something?

Could you maybe provide your EN-Log here, so that I can see what happens there?

How to export Exposure Notificaiton Logs under iOS 13.7 or newer

_This log does not conatin any private information, but the number of encounters._

German:

Einstellungen ➡️ Begegnungsmitteilungen ➡️ Status von Begegnungsaufzeichnungen ➡️ Begegnungsüberprüfungen ➡️ Überprüfungen exportieren

English:

Settings ➡️ Exposure Notifications ➡️ Exosure Logging Status ➡️ Exposure Checks ➡️ Export Exposure Checks

To upload the file here, rename it form .json to .txt

[ellenkoenig]

@Ein-Tim Restarting the app didn’t help. I don’t want to restart my phone right now.

Here is the log:
ExposureChecks-2020-12-20.zip

[Ein-Tim]

Okay, thanks for sharing your log @ellenkoenig.

This is very weird because a check happend today at 19:09 and also one at 15:08.
But I see the "MatchCount" in your log and this is not normal under 1.9.1. So, could you please make sure that you are really using 1.9.1?
Also, you are not using iOS 14.3 but iOS 14.2, but I don't think that this has to do something with it.

[ellenkoenig]

@Ein-Tim I updated a few hours ago to whatever was the most recent version offered. What else could I do?

[ellenkoenig]

@Ein-Tim Here is the Update confirmation.

[ndegendogo]

@ellenkoenig ENF error 13 means: the API was called too often - see here.
I suggest that you wait until tomorrow, and try then again.
Please report if this helped.

[ellenkoenig]

@ndegendogo

@ellenkoenig ENF error 13 means: the API was called too often - see here.
I suggest that you wait until tomorrow, and try then again.
Please report if this helped.

Sure, that might or might not help. The inconsistent thing about this error is that I didn’t open the app in the 24 hrs before updating. So how could the API be called too often?

[Ein-Tim]

@ndegendogo
Yes she can wait but AFAIK this Error will prevent further calls to the ENF but they are happening here...

[ndegendogo]

how could the API be called too often?

@ellenkoenig you are absolutely right
I just checked your uploaded file and it shows 5 checks today - which is definitely not above any limit.
Do you remember at which time you upgraded to 1.9.1? Before or after the check at 19:09?

[ellenkoenig]

@ndegendogo I would say after the check at 19:09. Probably around 19:30-19:45ish.

[thomasaugsten]

After updating to v2 an exposure check will be enforced. The v1 checks will count into v2 this means in rare case it can happens the limit is already reached. Please follow the information and wait 24h.

[ndegendogo]

Thanks @thomasaugsten

so maybe Apple does not count max 14 checks per day, but calculates the limit with finer granularity ... and throws this error if the last check is less than 2 hours ago ... (just speculating ...)

[FallobstAmateur]

Hello, everybody,
I’m using iOS 14.3 and CWA 1.10.1 on a iPhone SE 2016. Since yesterday I got always the notification mentioned above. Restarting my iPhone and waiting for 24 hours, as mentioned in the app’s FAQs didn’t help. This is the actual screenshot:

[ellenkoenig]

Oh, apologies, I forgot to report back. Waiting 24h did fix the issue for me back then. Now the app is working again as it should.

[Ein-Tim]

@FallobstAmateur
Could you please provide a screenshot from the main screen of Corona-Warn-App without the error message?

Additionally you could provide your EN-Log here, so we can see if the Exposure Checks are working.

How to export Exposure Notificaiton Logs under iOS 13.7 or newer

_This log does not conatin any private information, but the number of encounters._

German:

Einstellungen ➡️ Begegnungsmitteilungen ➡️ Status von Begegnungsaufzeichnungen ➡️ Begegnungsüberprüfungen ➡️ Überprüfungen exportieren

English:

Settings ➡️ Exposure Notifications ➡️ Exosure Logging Status ➡️ Exposure Checks ➡️ Export Exposure Checks

To upload the file here, rename it form .json to .txt

If you don't want to provide the log, please simply provide a screenshot from the Begegnungsüberprüfungen screen.
Thank you!

[FallobstAmateur]

Hello,

I added the EN-Log as a Word-Document; hopefully it will work for you. It’s
been quite difficult to get this log into this specific mail...

The next screenshot will be sent via GitHub.

Many thanks
Torsten Muth-Huber

Ein_Tim [e-mail] schrieb am Sa. 2. Jan. 2021 um 18:58:

@FallobstAmateur https://github.com/FallobstAmateur
Could you please provide a screenshot from the main screen of
Corona-Warn-App without the error message?

Additionally you could provide your EN-Log here, so we can see if the
Exposure Checks are working.
How to export Exposure Notificaiton Logs under iOS 13.7 or newer

This log does not conatin any private information, but the number of
encounters.

German:

Einstellungen ➡️ Begegnungsmitteilungen ➡️ Status von
Begegnungsaufzeichnungen ➡️ Begegnungsüberprüfungen ➡️ Überprüfungen
exportieren

English:

Settings ➡️ Exposure Notifications ➡️ Exosure Logging Status ➡️ Exposure
Checks ➡️ Export Exposure Checks

To upload the file here, rename it form .json to .txt

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753508809,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJGTUAU35HKQACPIYHDSX5NFTANCNFSM4VA2WDEA
.

[FallobstAmateur]

@Ein-Tim
Good Evening,
as promised, here are two new screenshots:
and after deleting this notification:

[Ein-Tim]

Okay interesting, thank you for sharing @FallobstAmateur.

The last successful exposure check was today at 12:17.
But I can't really tell why this message pops up. Sadly the upload of your log file did not work, could you maybe simply open up your phones settings and then follow these steps:

Begegnungsmitteilungen ➡️ Status von Begegnungsaufzeichnungen ➡️ Begegnungsüberprüfungen ➡️

From the screen you see then you can make a screenshot and upload it here, then I can see when (if) the checks happen...

When did you update to 1.10.1?
Did you get this message since you upgrade to 1.10.1 or did it start randomly?
Did you use 1.9.1 before or did you update from a later version?

[FallobstAmateur]

Ein_Tim [e-mail] schrieb am Sa. 2. Jan. 2021 um 19:52:

Okay interesting, thank you for sharing @FallobstAmateur
https://github.com/FallobstAmateur.

The last successful exposure check was today at 12:17.
But I can't really tell why this message pops up. Sadly the upload of your
log file did not work, could you maybe simply open up your phones settings
and then follow these steps:

Begegnungsmitteilungen ➡️ Status von Begegnungsaufzeichnungen ➡️
Begegnungsüberprüfungen ➡️

From the screen you see then you can make a screenshot and upload it here,
then I can see when (if) the checks happen...

When did you update to 1.10.1?
Did you use 1.9.1 before or did you update from a later version.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753515108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJC6LMTKJLMUIQW5IFLSX5TOVANCNFSM4VA2WDEA
.

[FallobstAmateur]

Most of my apps are programmed for automatic upgrades.. so this version
should have been installed quite early and is supposed to be based on
version 1.9.1. I’ll try to get more information from my iPhone...

Ein_Tim [e-mail] schrieb am Sa. 2. Jan. 2021 um 19:52:

Okay interesting, thank you for sharing @FallobstAmateur
https://github.com/FallobstAmateur.

The last successful exposure check was today at 12:17.
But I can't really tell why this message pops up. Sadly the upload of your
log file did not work, could you maybe simply open up your phones settings
and then follow these steps:

Begegnungsmitteilungen ➡️ Status von Begegnungsaufzeichnungen ➡️
Begegnungsüberprüfungen ➡️

From the screen you see then you can make a screenshot and upload it here,
then I can see when (if) the checks happen...

When did you update to 1.10.1?
Did you use 1.9.1 before or did you update from a later version.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753515108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJC6LMTKJLMUIQW5IFLSX5TOVANCNFSM4VA2WDEA
.

[Ein-Tim]

Thank you @FallobstAmateur.

[FallobstAmateur]

Okay, the Update was done on New Year’s Eve, but I can’t guarantee that the
predecessant version was really 1.9.1. Sorry @Ein-Tim

Ein_Tim [e-mail] schrieb am Sa. 2. Jan. 2021 um 20:04:

Thank you @FallobstAmateur https://github.com/FallobstAmateur.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-753516427,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKROJC6QB5RL7PFCQQMWIDSX5U4RANCNFSM4VA2WDEA
.

[Ein-Tim]

Okay no problem @FallobstAmateur.
Sadly, I can't help you any further here. You could wait another 24h and then report back here.

@thomasaugsten maybe you could quickly jump in here?

[Ein-Tim]

Hey @FallobstAmateur

Did anything change, or are you still getting this Pop-Up?

[FallobstAmateur]

Hallo @Ein-Tim
I've restarted the iPhone and wanted to wait until tonight to check once again how the app will react. I'll keep you informed..

[FallobstAmateur]

Good Evening to everyone and @Ein-Tim,
tonight's trial has been successful. The EN-Log shows three Updates today, but the app hasn't shown the error code anymore.
Thanks for your assistance.

[dsarkar]

@FallobstAmateur, Happy to hear, and many thanks for the feedback!
@Ein-Tim, Thanks !

[yannikbloscheck]

Just started to have the same issue with the app version 1.10.1 under iOS 14.3. Doesn't update automatically or manually. Used the app for several versions on this device.
Logs

[dsarkar]

@yannikbloscheck Thanks for reporting. Please, wait for at least 24 h. Feedback will be very much appreciated. See https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issue-770687899. Best wishes. DS

---

Corona-Warn-App Open Source Team

[Ein-Tim]

I don't really understand where this message is coming from, looking at the log from @yannikbloscheck there were only 3 checks in the last 24h, this should only be shown if there were more than 6 checks in the last 24h.
Are you trying to fix this or is somebody investigating why this is happening?

cc @thomasaugsten

[thomasaugsten]

It is hard to investigate its is very likely that the exposure checks fails but Apple still counting it in the rate limit. I assume their are only a few cases and it is gone after 24hr

[yannikbloscheck]

It's now working again. Here is the current log now after.

From the error code it has to be the rate limit, but like with other errors before (#1000) a big question is why it isn't it just handled better by the app.
Instead this error message pop ups again and again, because the apps tries automatically again. The coloured background for the risk is gone and instead there is a dangerous sounding message "Risiko-Überprüfung fehlgeschlagen". Annoying the user gives him the impression that the app doesn't work while it actually does. In my case the last successful exposure comparison was just four hours ago. So no need for all the communicated drama.
It would be better to stop these error alerts and instead show a message next to the last updated date while keeping the coloured background for the risk and the big risk classification text. I would keep showing the button to manually trigger the exposure comparison in that case and provide an error alert dialog just when the button was used unsuccessfully.

[ndegendogo]

@thomasaugsten what exactly is the implemented behaviour in cwa 1.10 when I open the app? In previous versions it triggered a risk check - is this still the same in 1.10?
Before 1.10 most users did not open the app frequently; but this has (hopefully) changed with the contact diary feature.

[thomasaugsten]

It will trigger not at every start. Every 6h if there a new key files downloaded.

[ThisIsNotALoveSong]

Hi,
Version 1.10.1 (0)
IOS 14.3

same behaviour as Fallobst described 4 days ago.
I did a lot of refresh in the last 4 hours.
Any clues?
thanks!

[Ein-Tim]

Hey @ThisIsNotALoveSong
Please wait 24h and report back, thanks.

[dsarkar]

Hi @ThisIsNotALoveSong. Thanks for reporting. All should be back to normal after 24 h as @Ein-Tim said. In any case we will appreciate your feedback then. Thanks.

[ThisIsNotALoveSong]

@dsarkar
worked early this morning again. Thanks!

not funny: using the app since day 1.
Needed it for the first time waiting for a test result,
so i refreshed the app a lot of times.
Obviously refreshing stresses the app and throws
an userunfriendly error sending me to github.
I told my story and you guys told me to wait for the next refresh 24h
( what i didnt do waiting for the test)
( dont get me wrong, you were very fast and helpful,
I appreciate that)
To emphasise it: you use the refresh a lot of times
When you wait for a test result and then the app goes down?
Giving this error message and error dealing via github?
Cmon - you must be kidding, i am sure 95% of the app users are
not able to get in contact with you via github.

Rest of story:
first my doc, called me to tell me i am positive,
then my healthdepartment called and finally after
4 hours the app went positive.
On my phone no contact to anyone was detected
Within the last weeks.
All my family members didnt get a warning on their mobiles..
Sure the app does what it should?

[ThisIsNotALoveSong]

Achja - kacke übrigens, wenn die Kommunikation hier auf Englisch läuft und man
Fehlermeldungskommentare für jedermann hier erfassen lässt...
Oder bin ich hiereinfach falsch?

[Ein-Tim]

Hey @ThisIsNotALoveSong

Just before I answer your questions, the answer why we are speaking English can be found here.

Needed it for the first time waiting for a test result,
so i refreshed the app a lot of times.

The ENError 13 alert has absolutely nothing to do with the test result process so even if you clicked "Aktualisieren" inside of the box which showed „Ergebnis liegt noch nicht vor“ very often, this has no impact on Issues like ENError13.

I told my story and you guys told me to wait for the next refresh 24h

The In-App pop-up also includes this information. The button "Mehr Erfahren" links to this FAQ entry.

When you wait for a test result and then the app goes down?

As said before, no. The ENError 13 comes from the underlying API, the Exposure Notification Framework, from Apple & Google. It shows up when your risk detection has been carried out more than 6 times in 24h.
Since CWA 1.9.1 there are some rare cases in which this error pops up although there were less than 6 checks in the last 24h.

On my phone no contact to anyone was detected
Within the last weeks.
All my family members didnt get a warning on their mobiles..
Sure the app does what it should?

You said you are using the App since one day. If you had „Risiko-Ermittlung“ active the whole time AND there were other phones near your phone, these will be warned (either „Low-Risk encounter“ or „High-Risk encounter“. More detailed information how the warning process works can be found here).

[ThisIsNotALoveSong]

Hey @Ein-Tim,

thanks for your explanations.
ok-so why don‘t you catch the API error and supress the Exception or throw a message for enduser.

Concerning my app install date:
that was a misunderstanding:
I am using the app since the first day available
to download in app store- not just 1 day.
The phones in my house (IOS and Android) were often quite close together-i understand the principles it should work bit obviously it didnt in my case.

[Ein-Tim]

@ThisIsNotALoveSong

thanks for your explanations.
ok-so why don‘t you catch the API error and supress the Exception or throw a message for enduser.

There are some ENErrors which are not shown to the user, but since the ENError (normally) has a big effect on the risk calculation (next check can be done earliest in 24h) the devs decided to show it.

that was a misunderstanding:
I am using the app since the first day available
to download in app store- not just 1 day.

Oh okay I see, I understood you wrong 😅

The phones in my house (IOS and Android) were often quite close together-i understand the principles it should work bit obviously it didnt in my case.

No phones which were close sho encounters? Not even green ones?
This is always hard to investigate because of the high data protection of CWA...

[ThisIsNotALoveSong]

I understand that you want to show the error, but please keep in mind, normaly this message comes up to a normal user - he doesnt understand anything and is unsure what is happening.
He wants to know he has to wait for 24h but the rest of functionality i working poperly.

What you get from user perspective:
In my case i waited for the test
and got the error message.
To reflect the problem you have to go to github, read your Development and technical advises.
After some reading i understood the problem-but i am sure that you are loosing 98 percent of the users.
And furthermore, they are left unsure if the other application parts are still working.

[dsarkar]

@ThisIsNotALoveSong, Thanks for all your detailed input. We will bring forward to the developers your thoughts about showing and interpreting this error message for a "normal" user.

@Ein-Tim Thanks for replying in detail.

[Ein-Tim]

@ThisIsNotALoveSong

this message comes up to a normal user - he doesnt understand anything and is unsure what is happening.

I disagree.
Affected users will see this:

A click on "Mehr Erfahren" will bring the user to a FAQ entry which explains everything in detail.

So or so this is o/t here so...

[ThisIsNotALoveSong]

@Ein-Tim:
yes this ist the message.
But when you wait for response for your corona-test and you are not sure wether this affects you or not.

[ndegendogo]

first my doc, called me to tell me i am positive, then my healthdepartment called and finally after 4 hours the app went positive.

@dsarkar could you please ask the devs what is the current frequency of background task to poll for test results?
I am aware that risk checking procedure is rate-limited to intervals > 4 hours from Apple side, and that a high frequency of BG task always eats a lot of battery.

[thomasaugsten]

The background task for test result fetching is scheduled for earliest time. At the moment our background task is executed every 2h. But this is influenced by the situation of the iPhone. With high usage, low battery or no internet the fetch is postponed. Test result fetching, key download and exposure check is executed in the same background task.

[ndegendogo]

Thanks @thomasaugsten.

As far as I understand, the key fetching is performed only while WLAN is availabe.
Does the same constraint apply also to fetching the test results?

[thomasaugsten]

Hourly key Download via wifi
Daily key download and 2h test result fetching via mobile and wifi

[ndegendogo]

@thomasaugsten is it possible to "poll" manually more often when I am waiting for a test tesult? Even when I don't have WLAN at that time, only mobile data?
Because a delay of up to one day seems quite much in this situation (so it could be worth an enhancement request)

[thomasaugsten]

Open the app will refresh the test result and there is a refresh button in the test result pending screen

[Ein-Tim]

I suggest to close this (like #1703) since I think that with the FAQ articles in place and the today released version 1.12 everything should be clear.
If there are any duplicates we can reopen this for long-term visibility.

[dsarkar]

@ouboub Do you want to close this issue as suggested by @Ein-Tim? Thanks.

[ouboub]

done

On Thu, Feb 11, 2021 at 8:42 AM dsarkar [e-mail] wrote:

@ouboub https://github.com/ouboub Do you want to close this issue as
suggested by @Ein-Tim https://github.com/Ein-Tim? Thanks.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/corona-warn-app/cwa-app-ios/issues/1715#issuecomment-777255324,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNOMU6WF3J7CB5BOMW2ORLS6OC65ANCNFSM4VA2WDEA
.

[dsarkar]

@ouboub Thanks!

[dsarkar]

Related Internal Tracking ID: EXPOSUREAPP-4906