-
Notifications
You must be signed in to change notification settings - Fork 283
Error during exposure logging / EN Code: 16 #1000
Comments
Which version of iOS are you running? |
iOS 13.6 and Corona Warn App 1.1.2 |
@GPclips could you help here please? |
Hello @tibor, thanks for sharing. I will contact the development team and label it as a bug, to make sure this will be handled as soon as possible. @Ein-Tim thanks for your great support! Best Regards, Corona-Warn-App Open Source Team |
Steps to reproduce: I'm not entirely sure, but I think I opened a push notification from the app and got this in app alert. It's either this or I manually opened the app. |
Hi @tibor , |
@haosap for now only once |
If it only occurs once, I think it is pretty hard to reproduce. |
I had the same issue today. I just manually opened the app. It apparently also just refreshed. So there might be a relation there. |
Couldn't reproduce it today, but given the error explanation in the Apple documentation (if I guessed right and it's the actually framework error code) it should not be forwarded to the user, but simply handled by the app (for example retrying after a few seconds). |
Got it after opening the app (I don't open the app regularly, only every now and then). The UI shows "Updated at 11:02", the same time as when I opened the app, so the error could maybe be related to the sync. iOS 14 beta 6 |
Seeing exactly the same @DerLobi |
I experienced this error as well a few days ago. It seemed to have no effect, though. The app updated itself as I tapped "Find out more" which is a no-op, as others have mentioned. Even if it's not easily reproducable, I think we can agree that it can be handled better:
(source: https://developer.apple.com/documentation/exposurenotification/enerror/code/datainaccessible) It seems strange to me that the device must be unlocked for Exposure Detection to take place (this again defeats the functionality of the background job). IMHO this should be clarified with Apple. In any case it's not helpful displaying this error to the user who - at this point - obviously has unlocked the device already. 😉 |
Hi, same issue here - iPhone SE (old) - latest iOS, latest corona warn app - error occurred under 13.6.1 and re-occurred after ios update to 13.7 and seems to be correlated with massive battery consumption (draining 25%+ of remaining battery charge over night in both cases). Might be stuck at attempt to connect for data update over night, supported by observation that server data was only updated after actually accessing application. Not observed, yet, with iPhone SE 2020. Update: just checked, it seems app was updated yesterday, so it seems the bug survived the update. |
Thank you, everyone, for the additional feedback. The internal Jira ticket was updated with your additional information. Best regards, Corona-Warn-App Open Source Team |
@sfaxiaberlin do you remember the context when this error message popped up? Did you just open the app before? Did you return from a submenu? Or was the app just open and you were looking at the status? Do you remember if the screen was locked? And: could you please give your cwa version as well? Thanks. |
Version 1.3.2 (0) |
Disclaimer: I am not one of the project maintaimers here @sfaxiaberlin Thanks. Maybe you could investigate one more detail, and check the timestamps of your checks in the ENF log file. Was the time of this error message preceded by any unexpected pattern, like overly long delay of the check? |
Thanks a lot @dsarkar |
FYI, PR #1608. Best wishes, Corona-Warn-App Open Source Team |
Wow - this was fast! 😀😀😀 |
@ndegendogo, thanks! We will forward this also to the developers! Best wishes, Corona-Warn-App Open Source Team |
Same error here. "Find out more" only closes the dialog. |
Hi @techniker, Thanks for reporting. This problem is resolved and the solution will be implemented in a future release. Corona-Warn-App Open Source Team |
Thanks! :) |
@techniker, this should solve it #1000 (comment). |
Fixed with version 1.9.1. |
Dear community, Thank you for all your contributions. As @Ein-Tim says, this issue is fixed now. Thanks again! Best wishes, DS Corona-Warn-App Open Source Team |
I got an alert with the following message today:
An error occured during exposure logging. EN Code: 16
Tapping on „Learn more“ wouldn’t do anything except closing the alert popup.
Is there anything I would need to do as a user?
Internal Tracking ID: EXPOSUREAPP-2018
The text was updated successfully, but these errors were encountered: