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

VC_NAME_MISMATCH error upon adding second vaccination certificate #3645

Closed
raeior opened this issue Jul 6, 2021 · 7 comments
Closed

VC_NAME_MISMATCH error upon adding second vaccination certificate #3645

raeior opened this issue Jul 6, 2021 · 7 comments
Labels
bug Something isn't working

Comments

@raeior
Copy link

raeior commented Jul 6, 2021

Technical details

  • Device name: Moto g6 plus
  • Android version: 9
  • App version: 2.4.3

Describe the bug

When trying to add the second vaccination certificate the app shows a VC_NAME_MISMATCH error. Both documents containing the QR code show the same name. The only difference I can see is that the date of birth is formatted differently: YYYY-MM-DD vs DD.MM.YYYY. It is also possible that this is related to handling of a Dr. title as part of the name, but at least on the certificates both are written identically. The same certificates are accepted without problem by the CovPass App. I could work around this by deleting the first certificate from the app and just adding the second one but the behavior is still strange.

Steps to reproduce the issue

  1. Add first vaccination certificate (It does not matter for the occurrence of the bug if it is from the first or second vaccination)
  2. Add the second vaccination certificate
  3. See error

Expected behavior

Both certificates should be added without error, as happens in the CovPass App.

Possible Fix

Looking at the printed data on the sheets I would expect it to be related to either the different date format or some minor difference in how the Dr. title is written.

@raeior raeior added the bug Something isn't working label Jul 6, 2021
@vaubaehn
Copy link
Contributor

vaubaehn commented Jul 6, 2021

A response here could likely also answer #3547

@raeior
Copy link
Author

raeior commented Jul 6, 2021

Huh, no idea how I missed that report. Name capitalization is the same for both certificates in my case.

@dsarkar
Copy link
Member

dsarkar commented Jul 6, 2021

@raeior Thanks for reporting.

Workaround: Delete all vaccination certificates and just scan the second one. IMMUNTY should be displayed after 14 days of the second vaccination.


Corona-Warn-App Open Source Team

@vaubaehn
Copy link
Contributor

From the response in #3547 it's now confirmed that for matching all certificates to the right person the birthdate and standardized names are used.

In @raeior 's case it seems to be that the birthdate didn't match:

The only difference I can see is that the date of birth is formatted differently: YYYY-MM-DD vs DD.MM.YYYY

But also when the standardized names are not entered or generated correctly, a mismatch of certificates can occur:
#3670
corona-warn-app/cwa-quick-test-frontend#185

In these cases it would only help to get the "wrong" certificate re-issued correctly.

@MikeMcC399
Copy link
Contributor

@raeior

In the announcement for version 2.13 of the Corona-Warn-App it describes an enhancement which might have solved your issue:

"In addition, the project team has improved the algorithm when assigning certificates to people. The Corona-Warn-App now assigns certificates with spelling errors in the name to the same person.

Previously, errors such as a different number of spaces between a person's first and last name caused the Corona-Warn-App to assign these certificates to two different people. This changes with version 2.13. For this reason, a certificate may no longer be displayed in the overview under the "Certificates" tab. However, the certificate has not disappeared, but is then displayed in the certificates section under the name of the corresponding person. Users can access it by tapping on their name under "Certificates"."

@MikeMcC399
Copy link
Contributor

@raeior

I believe this issue can be closed because:

  1. Certificates can be successfully scanned from multiple people (https://www.coronawarn.app/en/blog/2021-07-12-cwa-version-2-5/)
  2. The matching of certificate names has been made more robust (see https://www.coronawarn.app/en/blog/2022-03-16-cwa-2-19/)

Do you have any remaining issues with your certificates?

@MikeMcC399
Copy link
Contributor

The error code VC_NAME_MISMATCH no longer exists in current versions of the app, so it would be impossible for it to appear.

This is from the old 2.4 version:

Since the error can no longer occur, this issue should be closed.

@mtwalli mtwalli closed this as not planned Won't fix, can't repro, duplicate, stale Sep 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants