[Overview] References, e.g. error codes

[dsarkar]

Index

Apple/iOS EN error codes
Google/Android EN error codes

Questions on the downloaded keys

---

Corona-Warn-App Open Source Team

[MikeMcC399]

@dsarkar
Somehow I deleted the comment

For the sake of readability I edited out the comments in #499 (comment) so it is left as a reference positing.

You could also hide or delete the posting #499 (comment) you marked as obsolete, again for the sake of readability.

[Ein-Tim]

Apple/iOS ENError codes

---

The codes can also be found here, in the official developer documentation from Apple.

1 unknown
Failure has an unknown cause.
GitHub issues:
FAQ/workaround:

2 badParameter
The parameter is missing or incorrect.
GitHub issues: corona-warn-app/cwa-app-ios#1353, corona-warn-app/cwa-app-ios#1359
FAQ/workaround: https://www.coronawarn.app/en/faq/#ios_black_screen

3 notEntitled
Process of calling is not entitled.
GitHub issues:
FAQ/workaround:

4 notAuthorized
The user has denied access to the notification framework.
GitHub issues:
FAQ/workaround:

5 unsupported
Operation is not supported.
GitHub issues: corona-warn-app/cwa-app-ios#766
FAQ/workaround: https://www.coronawarn.app/en/faq/#ENError5

6 invalidated
A call to invalidate before the operation completes normally.
GitHub issues:
FAQ/workaround:

7 bluetoothOff
Bluetooth is turned off.
GitHub issues:
FAQ/workaround:

8 insufficientStorage
The storage is insufficient to enable notifications.
GitHub issues:
FAQ/workaround:

9 notEnabled
Notification is not enabled.
GitHub issues:
FAQ/workaround:

10 apiMisuse
The API use is incorrect.
GitHub issues:
FAQ/workaround:

11 'internal'
A bug in the internal notification framework.
GitHub issues: corona-warn-app/cwa-app-ios#759, corona-warn-app/cwa-app-ios#972, corona-warn-app/cwa-app-ios#976, corona-warn-app/cwa-app-ios#983, corona-warn-app/cwa-app-ios#1284, corona-warn-app/cwa-app-ios#1296,
FAQ/workaround: corona-warn-app/cwa-website#244, https://www.coronawarn.app/en/faq/#ENError11

12 insufficientMemory
The memory is insufficient to perform the operation.
GitHub issues:
FAQ/workaround:

13 rateLimited
API calls are too frequent.
GitHub issues: corona-warn-app/cwa-app-ios#759, corona-warn-app/cwa-app-ios#1353, corona-warn-app/cwa-app-ios#1715
FAQ/workaround: https://www.coronawarn.app/en/faq/#ENError13

14 restricted
Exposure notification is disabled due to system policies.
GitHub issues:
FAQ/workaround:

15 badFormat
A file is formatted incorrectly.
GitHub issues:
FAQ/workaround:

16 dataInaccessible
The user must unlock the device before it can access data.
GitHub issues: corona-warn-app/cwa-app-ios#1000, corona-warn-app/cwa-app-ios#1608,
FAQ/workaround:

17 travelStatusNotAvailable
The system can’t determine whether the user is traveling.
GitHub issues:
FAQ/workaround:

---

GitHub issues/pull requests related to iOS error handling in general:

• Exposure Submission Flow - Error Alert adjustments cwa-app-ios#843
  Handle the ENError 5, 11, and 13. All of them now have an Alert Action "Mehr erfahren" that leads you to the FAQ.
• Missing default action for "More Information" button in EN Error popup cwa-app-ios#1353,
  Missing default action for "More Information" button in EN Error popup
• Risk Calculation Errors - Alert Refinement cwa-app-ios#868
  This PR adds some more details, as well as links several ENErrors to their corresponding FAQ entries

[Ein-Tim]

To be deleted afterwards

@dsarkar you could update the index and (if you don't plan to use this for Android error codes too) you could change the title to iOS error codes only (move to iOS Repo?).
@MikeMcC399 Maybe you could delete this comment for better readability.

Thank you!

[dsarkar]

@MikeMcC399 @Ein-Tim
Apparently by mistake I deleted @MikeMcC399 comment with the android codes. Very sorry about it. I will write it down again.

[MikeMcC399]

@dsarkar
Have you considered using https://github.com/corona-warn-app/cwa-app-android/wiki to set up and maintain such a list?

It seems that (mis-)using https://github.com/corona-warn-app/cwa-documentation/issues doesn't really lend itself to cleanly maintaining information like this.

[dsarkar]

@MikeMcC399 Wiki seems like the correct approach. Will check internally. We still can use the issues to maintain the wiki (mirror issue to wiki after community feedback.).

[dsarkar]

@MikeMcC399 we had a quick look into the wiki approach:

• Will look nice and neat
• Members can change directly in the browser and could copy/paste community contributions
• However, it not so easy for community members to contribute on Wiki pages, unfortunately. GitHubDesktop can't be used for PR for GitHub Wikis, there are workarounds on the command line.

[MikeMcC399]

@dsarkar
If you use wikis just for content which does not change much, like references to error messages, I think that could work.
If that doesn't actually work well, we could create one or more new .md documents and use that method instead.

[MikeMcC399]

@dsarkar
If this is going to be about iOS and Android error codes, it might be better to add a new Wiki to each of the corresponding app repos where the information belongs more logically. The documentation repo is more generic in most cases.

[MikeMcC399]

@dsarkar

The link to the Google ExposureNotificationStatusCodes was never replaced here and apparently nobody noticed.

Probably in the meantime the CWA Android app handles the error codes well and does not normally expose the user to strange / unexplained error codes any more.