-
Notifications
You must be signed in to change notification settings - Fork 285
Compatibility issues on iOS 14.2 (b3) #1339
Comments
@Mihahn |
According to Apple documentation, this error means bad parameters. Please check the ENF log if the check was done. |
@ndegendogo |
I see this too. Initially getting the error mentioned above. By now the error has changed to "Fehler 13: Ihre Risiko-Ermittlung für den heutigen Tag wurde bereits durchgeführt. [...]" |
@jkreileder I recommend that you are patient till tomorrow.... |
ooops .... it is late today. I just wrote a completely unrelated statement here - it was meant for a different thread. |
@Ein-Tim hopefully, yes ... |
@mihan @ftonat @jkreileder which iOS version were you running before you upgraded to this beta? |
@ndegendogo 14.2 beta 2. Worked flawlessly. |
Can also reproduce this error after updating from iOS 14.2 Beta 2 to Beta 3. It worked fine on b2 previously. |
Same here |
Went from iOS 14.2 b2 to b3 |
Same here! |
Same problem here after upgrading from 14.2 Beta 2 to 14.2 Beta 3. I uninstalled CWA and reinstalled it. Now it appears to be working again. |
Same here, no error after reinstalling. But until now there's an unknown risk (old checks remain in Apple's Exposure Checks but there hasn't been a check since reinstalling the app, so I can't confirm everything's up and running again). |
Same problem here with app version 1.3.2 (0) after having updated to iOS 14.2 Beta 3. I also noticed that clicking the "Mehr erfahren" button in the shown alert has no action. The alert window simply closes, as it does when selecting "OK". Having opened the app a couple time for testing this, the message of the alert has now changed to "Fehler 13: Ihre Risiko-Ermittlung für den heutigen Tag wurde bereits durchgeführt. …" |
@cmittendorf just for the record: which was your previous iOS version before this update?
With such an error code ( 2 meaning bad params) there are not so many options what a user could do. Except reporting back to the project maintainers or the technical hotline... (and, you are right, this could be the advice here).
with this error code you should be patient till tomorrow ... You could try the procedure that helped other users here: delete and reinstall the app. |
@ndegendogo The previous iOS version was 14.2 Beta 2. And I will simply be patient and wait till tomorrow … |
@ndegendogo Killing the app (or restarting the iPhone) didn't have an effect on error 2 and 13. Error 13 might have been caused by opening the app too many times yesterday. |
Hey everyone, I have created a Jira ticket Thanks again for your input! Best regards, Corona-Warn-App Open Source Team |
It is possible that there has been a change between the release of the developer beta and the public beta (released early hours today DE time) but I am not seeing the same error. App opens fine with no errors (iPhone 11, iOS 14.2 Public Beta 3) |
@davidm2781 the build number of developer beta 3 is 18B5072f. You can check the build number of the public beta in Settings/General/About, click on Software Version once to reveal the build number. |
can confirm 14.2 B3 (Developer BETA build 18b5072f) CWA Start results in Error EN Code: 2. |
@thomasaugsten thanks for the clarification 🙂 |
just updated to iOS 14.2 B4 and for me CWA working again. (With CWA 1.5.0) |
Keys are exchanged again. Full Log is visible in ENF Settings :-) iOS 14.2 B4 (18B5083a) |
Is that version already available, I don't see it in the software updates yet on my phone... |
Yes it is – until now it's developers only. But public beta should be released shortly after... I still have a question: When beta 4 fixes the issue, will it download the exchanged keys of the last week since the app stopped working? Or was the whole background key exchange process broken and it'll start after updating to 14.2 beta 4 again? If that's the case, I assume that all contacts from the past 7 days weren't recorded? |
@Mihahn |
@Mihahn - just my 2 ct on your question ... We have to distinguish two functions here:
And, finally: you can see the hash values of the key files for matching in the iOS settings ("Begegnungsmitteilungen") or in the json file export. And "somewhere in the internet" there is a list of the hashes of all key files published so far, so you can verify yourself that you did not miss any (I have to search the link again ...) @daimpi iirc it was you who knows this link? |
iOS 14.2 B4 did fix the original issue mentioned in the issue description so this Issue will be closed. The linked Jira issue is also marked as resolved. You can continue the discussion here if you like but please open a new issue if there are any follow up topics. Thank you for your understanding! Best regards, Corona-Warn-App Open Source Team |
Thank you – this is good news! I guess (a) wasn't working properly, as I got new entries in ENF every time I opened up the (broken) CWA app, but there weren't any "new files" downloaded. But as you said, with b4 it's up and running again and yesterday evening 14 new files were downloaded and I'm good to go. So thanks again for the information 👍 |
Yes, ENF log is written by iOS. They don't know about cwa downloading the key files from the server. They are logging the files on which they perform the match. |
@ndegendogo |
This is promising. My iPhone 7 is still stuck at 14.2 B3 and did not receive an update push, yet. |
@depate |
You're correct. I missed that comment. However, thanks for pointing that out for me again. |
This is fine in principle: the counter for the number of active days is something which CWA stores and this number can be easily changed if e.g. CWA data is reset. The important thing are the keys though and those are not stored in CWA but inside the Apple Exposure Notification Framework (ENF). |
I am aware that this only a display/presentation issue. I've been running CWA all time across all 14.2 betas. Then the incompatibility with beta 3 popped up. At some point last week, I reinstalled the app and CWA with beta 4 give me this warning above..I am aware how to read it. It might be misleading to others... |
Ah ok sry I misunderstood your point then. Yes this is indeed confusing. There are lots of issues which concern this display of "active days", imho it would make sense to just drop it and be done with it (other ENF apps also don't have this): corona-warn-app/cwa-wishlist#102 |
@depate and all: |
Instant information, great! |
@sebastiancomsa For more and detailed Information see @ndegendogo's comment here: #1339 (comment) |
i had the same exact issue. it is resolved in ios 14.2 beta 4 (now available for developers & beta testers, Germany) |
iOS 14.2 Public Beta 4 solved the issue inside the app. |
On iOS 14.2 beta 3 there’s an error message as soon as you open up cwa. EN Code: 2. I hope this can be fixed asap.
Edit: it seems like every time I open cwa, it tries to fetch the keys but it doesn’t succeed. There are entries in the exposure checks in settings matching the times I opened cwa (5min ago, 7min ago, 9min ago etc.), but there are no “new files”.
Internal Tracking ID: EXPOSUREAPP-3272
The text was updated successfully, but these errors were encountered: