Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

By omitting the name a QR Code with invalid schema is generated #81

Closed
RalicaY opened this issue May 19, 2021 · 15 comments · Fixed by eu-digital-green-certificates/dgca-app-core-ios#37
Labels
bug Something isn't working

Comments

@RalicaY
Copy link
Collaborator

RalicaY commented May 19, 2021

QR_invalid_Schema

Describe the bug

If the name is omitted (it is NULL value) the issuer app generates a QR-Code with an invalid Schema. Das kann von iOS nicht eingelesen werden, während Android da

A sample QR Code and the data to generate it is attached,

Expected behaviour

Steps to reproduce the issue

Technical details:

Windows, Chrome

Possible Fix

Additional context

@RalicaY RalicaY closed this as completed May 20, 2021
@RalicaY RalicaY reopened this May 20, 2021
@ggrund-tsi ggrund-tsi transferred this issue from eu-digital-green-certificates/dgca-issuance-web May 21, 2021
@ggrund-tsi
Copy link

Hi, at the moment it looks like an iOS issue because the generated JSON is valid. (otherwise the qr-code will not be generated)
Not all name input fields are mandatory or required.
Maybe it is faster when we try to reproduce it toghether.
Regards, Gordon

@yspreen
Copy link
Contributor

yspreen commented May 21, 2021 via email

@RalicaY
Copy link
Collaborator Author

RalicaY commented May 21, 2021

Additional information:

  • The DGCA Android Verifier App reads the code but renders the certificate invalid, although the test ist negative and the signature is verifiable.

  • The IBM Verifier App does not read the code either.

@yspreen
Copy link
Contributor

yspreen commented May 21, 2021 via email

@ggrund-tsi
Copy link

Then I gess we have an translation issue. In TypeScript the non required name fields are not 'null'. They are 'undefined'.
And undefined fields are ignored in JSON. And it is valid with validator from jsonschema.
e.g.:
"nam": {
"fnt": "SOME<NAME"
}

What you expect?
Like this?
"nam": {
"fnt": "SOME<NAME",
"gnt": null,
"fn": null,
"gn": null
}

Or like this:
Like this?
"nam": {
"fnt": "SOME<NAME",
"gnt": "",
"fn": "",
"gn": ""
}

Last example is imho not correct.

Regards, Gordon

@yspreen
Copy link
Contributor

yspreen commented May 21, 2021

Will be closed by the PR above. Thanks @ggrund-tsi

@RalicaY
Copy link
Collaborator Author

RalicaY commented May 26, 2021

The problem persists in the current iOS Verifier App 1.0.1 available in App Center as of 26.05.21

@RalicaY RalicaY added the bug Something isn't working label May 26, 2021
@yspreen
Copy link
Contributor

yspreen commented May 26, 2021

That's because it's not fixed in 1.0.1, but in the current main branch. Please ask Hendrik what code he used for the release, because this cannot be fixed if he used the 1.0.1 tag. Thanks

@Hendrik-Schmidt-Schierhorn-TSI

1.0.1 is officially our current version. Let us get in touch to solve this asap.

@yspreen
Copy link
Contributor

yspreen commented May 26, 2021

Well did you use the main branch to build or not? I can create v1.0.2 with all these changes, but it needs to be approved, merged, you have to make a new build, upload it, not sure if it's worth it for this small issue. It'll be in the next release regardless. But since it's fixed in main, I think we can close the issue here

@Hendrik-Schmidt-Schierhorn-TSI

Of course I used the main-branch. Let us talk later directly about this, please.

@yspreen
Copy link
Contributor

yspreen commented May 26, 2021

Oh okay! Thanks for clarifying. It's a legitimate concern then, I'll investigate this. Thanks Hendrik

@yspreen
Copy link
Contributor

yspreen commented May 26, 2021

It's a problem with the release, not with the code. It's confirmed working on the main branch:
image

@yspreen yspreen closed this as completed May 26, 2021
@Hendrik-Schmidt-Schierhorn-TSI

I updated the Test-App with the actual App-Core-Version.

@RalicaY
Copy link
Collaborator Author

RalicaY commented May 26, 2021

I confirm, the correction has worked and the bug is no more there with the Verfier App 1.0.1 (3)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants