Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

ENErrorDomain-Fehler 2 #823

Closed
hansdampf01 opened this issue Jul 1, 2020 · 14 comments
Closed

ENErrorDomain-Fehler 2 #823

hansdampf01 opened this issue Jul 1, 2020 · 14 comments
Assignees
Labels
apple use to tag issues that are related directly to the Exposure Notification Framework itself bug Something isn't working community Tag issues created by community members further input needed Issue requires more input from the creator to be processed good first issue

Comments

@hansdampf01
Copy link

hansdampf01 commented Jul 1, 2020

69140163-7E5E-43BF-B967-0BC53D8F442A

Im getting attached error when opening the cwa app.
Im on iPhone 11 Pro Max 13.5 (17F75) (Jailbroken) and downloaded the App via Appstore. Currently using cwa version 1.0.3 (1) from 01.07.2020.
I got this also with the previous version.
Since I got this error on my device I thought it only happened to me due to the jailbreak and not using 13.5.1 / 13.6 beta.
However im also managing my companies devices with Intune in Azure and made the cwa app available for my companies mobile devices. Today a user opened a Ticket for the same issue. The user is on a non-jailbroken iPhone 11 with 13.5.1 and facing the same.
I already called the hotline shown in the cwa app and opened a ticket about the error.
Please feel free to contact if you need further details.

@hansdampf01 hansdampf01 added the bug Something isn't working label Jul 1, 2020
@inf2381 inf2381 added the apple use to tag issues that are related directly to the Exposure Notification Framework itself label Jul 3, 2020
@camelusferus

This comment has been minimized.

@jwildeboer
Copy link

Please be precise. Did you get error 2 or 11/13?

@camelusferus

This comment has been minimized.

@jwildeboer
Copy link

Please add your observations to #759 where error 11/13 is handled. This issue should only be about error 2. thanks!

@SebastianWolf-SAP SebastianWolf-SAP added the community Tag issues created by community members label Jul 10, 2020
@hansdampf01
Copy link
Author

hansdampf01 commented Jul 27, 2020

So mal Butter bei die Fische - wann fixt ihr das?
Das ging eine ganze Zeit lang am Anfang, dann habt ihr es kaputt gepatched.
Das Problem wird wohl bei User Enrollment von IOS 13 liegen.
Hinzu kommt jedesmal wenn die App geupdated wird, taucht der Erst-installations-Prozess in Dauerschleife auf der erst durch einen Neustart gefixt werden kann.

Video: https://youtu.be/HoOZkEV6t34

@SebastianWolf-SAP
Copy link
Member

The original post was on error 2. The new issue is something else - we would appreciate if you report that in a dedicated issue. We've seen such issues only after an iTunes backup restore - did you do something like that?

Moreover, please also report back to us here if you can reproduce error 2 on your device. If not, we would probably close this one as it can't be reproduced anymore.

Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team

@hansdampf01
Copy link
Author

Its happening on all devices which are intune managed enrolled in ios 13 user mode. Every open of the app will produce 2 warning windows about EN Error 2.

In regards of new error it happens after each update of the app on intune managed devices enrolled in user mode.
I can create a new issue for that.

My best shot is there is an error with ios 13 User Mode enrollment which is a brand new feature that enables you to manage mobile phones gdpr compliant.

@ghost
Copy link

ghost commented Sep 30, 2020

Hello @hansdampf01,

since it has been a while, I kindly like to ask you if this error still occurs?
Could you please give me quick feedback, that we can create an internal tracking id and share this with the dev team and/or Apple?

Also, if I understand you correctly this is happening whenever you open the application, is that correct?

Thanks,
LMM

Corona-Warn-App Open Source Team

@ndegendogo
Copy link
Contributor

Although not a precise duplicate, it seems to happen again now. Several users are reporting EN error 2 with current cwa version 1.3.2 after migration from iOS 14.2 beta 2 to beta 3 (#1339).

Could you please clarify with Apple? They should fix it before their final release of 14.2

@sebastiancomsa
Copy link

sebastiancomsa commented Oct 16, 2020

I'm also receiving the same error, when I tried to open the app today. I updated my iOS yesterday afternoon to version 14.2 (18B5072f).

Any suggestions? Re-install of the app? Maybe not the best to do and just wait for a fix?

Thanks,

Sebimage

@Ein-Tim
Copy link
Contributor

Ein-Tim commented Oct 16, 2020

@sebastiancomsa
Please see this comment from @thomasaugsten, the App doesn't work with iOS 14.2 Beta 3.

For everybody:
If you receive Error 2 on the iOS 14.2 Beta 3 please see this Issue: #1339

@sebastiancomsa
Copy link

@Ein-Tim i hope this will be fixed soon, I also reported this to Apple via their feedback tool. So hopefully they will also look into this from their side of the Exposure logging code in iOS.

Thank you for the updates though, will patiently wait to have this fixed. Will not expose myself in the meantime! ;)

@dsarkar
Copy link
Member

dsarkar commented Dec 4, 2020

Dear @hansdampf01, @sebastiancomsa, community,

We would appreciate feedback on this issue: Any reoccurrence with CWA 1.7.1?

Thanks. Best, DS


Corona-Warn-App Open Source Team

@dsarkar dsarkar added the further input needed Issue requires more input from the creator to be processed good first issue label Dec 4, 2020
@dsarkar
Copy link
Member

dsarkar commented Dec 7, 2020

Dear @hansdampf01, @sebastiancomsa, and community,

Thanks for all the contributions here. We will close this issue now. However, should this issue arise again, please re-open it.

Best regards, DS


Corona-Warn-App Open Source Team

@dsarkar dsarkar closed this as completed Dec 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
apple use to tag issues that are related directly to the Exposure Notification Framework itself bug Something isn't working community Tag issues created by community members further input needed Issue requires more input from the creator to be processed good first issue
Projects
None yet
Development

No branches or pull requests