search

corona-warn-app / cwa-app-ios

Native iOS app using the exposure notification framework from Apple. The CWA development ends on May 31, 2023. You still can warn other users until April 30, 2023. More information:
https://coronawarn.app/en/faq/#ramp_down
Apache License 2.0
1.68k stars 286 forks source link

ENErrorDomain-Fehler 5 #766

Closed christianneu closed 4 years ago

christianneu commented 4 years ago

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

  1. Open App
  2. Wait
  3. Popup opens 4 times quickly

Technical details

img_0260

thomasaugsten commented 4 years ago

Can somebody update to iOS 13.6 Beta 2 and recheck the error?

https://betaprofiles.com/ios13

kaisemarmuc commented 4 years ago

Can somebody update to iOS 13.6 Beta 2 and recheck the error?

https://betaprofiles.com/ios13 Sorry, I can‘t. Managed profile.

Launethil commented 4 years ago

Can somebody update to iOS 13.6 Beta 2 and recheck the error?

https://betaprofiles.com/ios13

Did the update to test this. Unfortunately still getting the same error and behavior.

thomasaugsten commented 4 years ago

@Launethil can you please contact me directly for a bug report

Launethil commented 4 years ago

@Launethil can you please contact me directly for a bug report

Sure thing. Mail is on its way. :)

marijoo commented 4 years ago

Same with iPhone 11.

zerbes commented 4 years ago

Currently upgrading to iOS 13.6 Beta 2 for testing

nrd-tx commented 4 years ago

Same here 13.5.1 Iphone 7 Message pops up 2 times after openIng the app Updated last time June 23rd (day before yesterday)

34F6EC7F-8A7E-45CA-BE93-A6DD43455CA0

Hubersan commented 4 years ago

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.

Same error here on iPhone SE (A1723) on iOS 13.5.1, normal private iPhone, not under MDM. No additional Corona App installed. Error 5 appears when opening the App.

zerbes commented 4 years ago

Upgrade to iOS 13.6 Beta 2 did not help, phone-diagnosis-data was forwarded to @thomasaugsten.

ronxorange commented 4 years ago

Same in SwissCovid app... with Iphone 11 Ios13.5.1 image

DanteFiligesto commented 4 years ago

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?

Hi, Due to the data privacy, we're not allowed to log any information. That's the reason, our dev team is trying to reproduce the bug. At the moment, we could not manage to do it.

This means that if I give you my iPhone you can’t get any information from it to analyze the problem? So I guess you are trying to reproduce using an app version with logging on? If so, can we give it a try and help reproducing? Data privacy should be my choice.

Filirator commented 4 years ago

Next day - same shit. SAP and Telekom are not able to fix the bug???

Hermann12 commented 4 years ago

Eine Woche hat es gedauert. IPhone11 IOS13.5.1 Deinstallation und Neue Installation bringt nichts, Fehler erscheint sofort wieder. 1B8F89C0-F5AC-4B63-8EA2-A39B45C1BC6B

hmentzer commented 4 years ago

I just reinstalled the app. Interestingly already during the setup process, immediately after it asks to activate the exposure logging, I got the ENErrorDomakn Error 5 again. I do not have any special setup, the device is an iPhone 8 and it runs iOS 13.5.1. The setup process was done using my device’s mobile data.

FabianClemenz commented 4 years ago

Same error on my Dads iPhone

  • iPhone 7 Plus, company phone (but unmanaged), iOS 13.5.1

The app just started working again on his phone 🤷🏻‍♂️

hauspost commented 4 years ago

Two iPhones in our household now show this error. iOS is updated, iPhones are 8 and 11 Pro, unmanaged, no special setup. happens in WiFi (Vodafone Kabel) and mobile (Telekom), does not happen while disconnected from internet. Last risk update on 23.06.2020. See photos. Video available as well.

Are there any news on this?

127DBEE3-9A73-4119-9066-81B1D578719A 0A811710-1DDD-4E06-9513-C973BA663323

tkowark commented 4 years ago

Next day - same shit. SAP and Telekom are not able to fix the bug???

@Filirator please watch your language. The team is working hard on narrowing down the issue and as you can see in this thread, reproducing it is just not trivial.

zerbes commented 4 years ago

My PiHole-logging shows the domain svc90.main.px.t-online.de tried to be reached which i can´t ping manually as well. No idea if that helps anyhow.

screenshot 21

DisappointedMoose commented 4 years ago

Same issue here. iPhone X iOS 13.5.1. Unmanaged phone.

Owner says the error started when came back to Germany from the Netherlands and was connected to a German mobile carrier again.

Other Android and iOS devices in the same network work fine.

christianbrb commented 4 years ago

@zerbes That's great.

The problem went away after deleting and updating the app, but also all data is gone (I'll create a separate issue to analyse that).

I also assume, that the matching is the problem as the first covid90 positive test results have been uploaded and the issue on my iphone only appeared afterwards.

Maybe issue https://github.com/corona-warn-app/cwa-backlog/issues/2 is related.

Groman123 commented 4 years ago

y PiHole-logging shows the domain svc90.main.px.t-online.de tried to be reached which i can´t ping manually as well. No idea if that helps anyhow.

I got an answer via ipv4 for that host. grafik

zerbes commented 4 years ago

y PiHole-logging shows the domain svc90.main.px.t-online.de tried to be reached which i can´t ping manually as well. No idea if that helps anyhow.

I got an answer via ipv4 for that host. grafik

Your system pings a IPV4, my tried a IPV6. Interesting to see the different behaviour. The IP 87.140.209.90 can be pinged manually as well here! screenshot 22

FabBaur commented 4 years ago

I had the same problem with the Swiss Covid App. For me, the error disappeared the second I was in contact with another iPhone Swiss-Covid-App User. Not sure if that helps in any way.

colu89 commented 4 years ago

Ive got the same issue. It started about 3 days ago. Iphone 7, 13.5.1. not managed.

lventimi commented 4 years ago

Since three days the same issue. Reinstalling the App doesn't cure the problem

IphoneSE IOS 13.5.1 WhatsApp Image 2020-06-26 at 10 42 20

christopher-wilke commented 4 years ago

Same Error here. I am using iPhone XR.

zerbes commented 4 years ago

I had icloud-service disabled or at least disabled the different types of data to be forwarded to icloud. Enabling it did not solve the issue for me

jantenne commented 4 years ago

@h3dgyy I have all services active, beside mail, calendar and contact which I drive via exchange

Filirator commented 4 years ago

icloud is enable

Launethil commented 4 years ago

iCloud services were enabled. I disabled them and restarted the phone -- still got the error. Re-enabled iCloud services, restarted the phone -- same problem.

I noticed that it takes "notably" more time for the error to pop up after a restart compared to just shutting down the app and reopening it. Only talking about one or two seconds, but it was long enough for me to think the error might have been fixed after the first restart. That probably means nothing, but I thought I'd mention it, just in case.

haosap commented 4 years ago

Hi @Launethil , Thanks for elaborating the issue. Due to lack the log of the app, we can only try to enumerate all the possibilities. We'll keep investigating the issue.

auxua commented 4 years ago

Same issue here (iOS 13.5.1, no mdm, dev profiles, iphone XR)

It started after some time at place near the belgian border (~1km), where the belgian provider nets where dominating the german ones.

A friend told me the same behavior after some time near the border too.

Are you others also located near to borders?

Hubersan commented 4 years ago

Hi All,

my son is located in the middle of Germany with his unmanaged iPhone SE. No borders anywhere near. I looked into his Kontaktprotokoll and obviously there was never a contact registered (we have at least 3 iPhones with the App in the house hold and 2 at relatives who were visited). My iPhone 8 works just fine, shows 3 contacts and has no error message 5.

Von meinem iPhone gesendet

Am 26.06.2020 um 17:21 schrieb auxua notifications@github.com:

 Same issue here (iOS 13.5.1, no mdm, dev profiles, iphone XR)

It started after some time at place near the belgian border (~1km), where the belgian provider nets where dominating the german ones.

A friend told me the same behavior after some time near the border too.

Are you others also located near to borders?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

jantenne commented 4 years ago

@Hubersan where do you see contacts made? Because I looked into the settings where the protocol should appear and this is empty. I thought it has to be like this. So mine is empty since the first day while I traveled also a lot.

Filirator commented 4 years ago

me too - no contacts since 10 days!

ST-KW commented 4 years ago

Same problem here (unmanaged IPhone SE first gen). My ping answers from Hamburg:

ping svc90.main.px.t-online.de

Ping wird ausgeführt für svc90.main.px.t-online.de [2003:2:20:701:87:140:208:26] mit 32 Bytes Daten: Antwort von 2003:2:20:701:87:140:208:26: Zeit=11ms Antwort von 2003:2:20:701:87:140:208:26: Zeit=10ms Antwort von 2003:2:20:701:87:140:208:26: Zeit=10ms Antwort von 2003:2:20:701:87:140:208:26: Zeit=10ms

Legacy IP also works:

ping -4 svc90.main.px.t-online.de

Ping wird ausgeführt für svc90.main.px.t-online.de [87.140.208.26] mit 32 Bytes Daten: Antwort von 87.140.208.26: Bytes=32 Zeit=12ms TTL=53 Antwort von 87.140.208.26: Bytes=32 Zeit=11ms TTL=53 Antwort von 87.140.208.26: Bytes=32 Zeit=12ms TTL=53 Antwort von 87.140.208.26: Bytes=32 Zeit=12ms TTL=53

image

The problem persists if I disable WLAN and use the app via LTE.

image

Reboots do not bring any changes either.

djaegerDe commented 4 years ago

Hi, I have the same problem on my private, unmanaged iPhone 11.

My contact protocol is empty, although another person in the household and people in the Office also uses the app and the contact log lists entries on their phones.

I tried disabling and enabling the „Risiko Ermittlung“ and restarted the phone, but this did not help.

I don't know if it helps, but I use Apple Family Sharing for apps and Apple services and this has led to some problems with other apps in the past. DD534AC0-F9FE-4137-B6EA-D2DF324E3D62

zerbes commented 4 years ago

What do we know until now?

Keep up the good work, dev-team, and chase that bug :)

Hubersan commented 4 years ago

Hi All,

on my iPhone 8 everything is fine and under Setttings\Corona-Warn I can go to the bottom (blue text) to see the Covid-19 Kontaktprotokoll - after authentication I see a log of my contacts with timestamp:

On my sons iPhone SE, there is not a single entry. He has this weird „Error 5“. I suspect, that there is not a small number out there with the App running - but with no effect, because it is virtually disabled.

On my company phone (iPhone SE, managed) I realized, that the App also disables all contact checking silently once the powersaving mode is on. I had accidentially turned it on (76% battery) and wondered why the App showed some kind of disabled state (red WLAN on this comic picture of the contact check). After disabling power saving and restarting the App all was fine. Different topic, but interesting to know.

Cheers, Peter

Von meinem iPhone gesendet

Am 26.06.2020 um 19:19 schrieb Steffen Zerbe notifications@github.com:

 What do we know until now?

german and swiss app face the same problem -> not DNS-related (can be solved and swiss app wob‘t use Deutsche Telekom domain with high probability

the problem did not show up on the android version of the app (yet)

most if the iphone-models supporting iOS 13.5+ show the error ->not model specific

it showed up spontanousy without any change to the installed app or iOS -> external factor?

Keep up the good work, dev-team, and chase that bug :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Hubersan commented 4 years ago

I just read about the Apple family sharing (Familienfreigabe). In our case out of 4 iPhones (SE, 2x8, 6) all work fine - except the SE. All unmanaged. We also use Familienfreigabe.

Von meinem iPhone gesendet

Am 26.06.2020 um 20:13 schrieb Peter Huber peter.ph.huber@mac.com:

Hi All,

on my iPhone 8 everything is fine and under Setttings\Corona-Warn I can go to the bottom (blue text) to see the Covid-19 Kontaktprotokoll - after authentication I see a log of my contacts with timestamp:

On my sons iPhone SE, there is not a single entry. He has this weird „Error 5“. I suspect, that there is not a small number out there with the App running - but with no effect, because it is virtually disabled. On my company phone (iPhone SE, managed) I realized, that the App also disables all contact checking silently once the powersaving mode is on. I had accidentially turned it on (76% battery) and wondered why the App showed some kind of disabled state (red WLAN on this comic picture of the contact check). After disabling power saving and restarting the App all was fine. Different topic, but interesting to know. Cheers, Peter Von meinem iPhone gesendet >> Am 26.06.2020 um 19:19 schrieb Steffen Zerbe : >> >  > What do we know until now? > > german and swiss app face the same problem -> not DNS-related (can be solved and swiss app wob‘t use Deutsche Telekom domain with high probability > > the problem did not show up on the android version of the app (yet) > > most if the iphone-models supporting iOS 13.5+ show the error ->not model specific > > it showed up spontanousy without any change to the installed app or iOS -> external factor? > > Keep up the good work, dev-team, and chase that bug :) > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or unsubscribe.
HoSch-193 commented 4 years ago

Since 20:25 my App is working again

christianbrb commented 4 years ago

@christianbrb What you mean with all information? The contact protocol can only reseted in the iOS settings. You have to onboard again and the last check date is gone but all keys are still available.

@thomasaugsten The contact protocol has been deleted with the deletion of the App.

I had ~10 days of contact tracing in the app and now it shows just 1 day.

thomasaugsten commented 4 years ago

@christianbrb This are two different things. Contact protocol is managed by the OS. The App shows how many days in a row it checked the downloaded keys against the contact protocol of the OS.

christianbrb commented 4 years ago

@thomasaugsten Thanks for your reply. I have created #794 to avoid sidetracking the issue.

christianbrb commented 4 years ago

Thinking about the issue, it first appeared on my phone while trying to download and match the first key file. Before the error appeared my “Kontaktüberprüfungen“ always showed 0 entries.

Has anything changed regarding the key data structure from 1.0.0.0 to 1.0.2.2 in the app, in the cwa-server or in the Android (app)?

hauspost commented 4 years ago

The app started working again on my phone yesterday evening. No more errors, and risk status is updated. From my side, no changes or reinstalls were made. The change happened while leaving the Hamburg region for the first time in weeks, driving to Cologne. Can’t imagine how this could be relevant, but who knows...

christianbrb commented 4 years ago

@hauspost The error appeared on my iPhone after significantly changing my location.

Maybe this is related to the region field in the header of exposition_notification.proto message (see https://github.com/corona-warn-app/cwa-documentation/blob/master/solution_architecture.md#data-format)?

MisterRios commented 4 years ago

My app stopped working on Wednesday. I kept getting this same error twice every time I opened the app. I have a Private IPhone 8.

This morning I was poking around in location services after keeping track of the comments here. I switched “Location Based Alerts” (in Settings -> Privacy -> Location Services -> System Services) to On, and then restarted the app. It immediately worked again.

I switched it back to off, and it still works, though who knows what will happen in 24 hours when it tries to update again.

Hope you find and squash the bug soon! Good luck!

svona-ai commented 4 years ago

Same issue here, iPhone XS with 13.5.1 unmanaged. Stopped working with this error about 2 days ago, realized it when traveling from Munich to Frankfurt (but may have stopped working before), had the last status update on 22 June. Deleted the app and reinstalled, still the same issue.