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?

[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 ***@***.***> 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 <#1715 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNOMU6WF3J7CB5BOMW2ORLS6OC65ANCNFSM4VA2WDEA> .

[dsarkar]

@ouboub Thanks!

[dsarkar]

Related Internal Tracking ID: EXPOSUREAPP-4906