Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Blanks in names cause special characters

See original GitHub issue

This bug contains personal data and could be of high priority.

Avoid duplicates

  • Bug is not mentioned in the FAQ
  • Bug is not already reported in another issue

Technical details

  • Device name: Google Pixel 3a
  • OS version: Android 11
  • App version: 1.95.12

Describe the bug

Since the updated version of CovPass introduced the field option standardized name, first name the app converts my name wrong. Because I’ve got a second first name (middle name) written with a blank character, the app converts the space into the following character: <. Any other characters are correctly displayed in caps. I have no problem in the upper view of the ‘normal’ namespace.

Steps to reproduce the issue

I scanned my certificate as I got the app (before the new feature was released). As I checked out the new feature, I realised that my standardized name is spelled incorrect. You could reproduce my issue trough importing a certificate with a middle name.

Since screenshots are blocked, it’s hard to proof my point here. But it looks like this:

Name, Vorname / name, first name Kelle, Leon Niklas Standardisierter Name, Vorname / Standardized name, first name KELLE, LEON<NIKLAS

This looks incorrect and could lead to problems during checks.

Expected behaviour

The standardized name field should convert blank spaces (eg. whitespaces) into blank spaces.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

thinkbergcommented, Sep 20, 2021

True, the dcc contains family and given name separately. I suggested already using either spaces and comma or the icao format.

thinkbergcommented, Sep 20, 2021

It’s not a bug. ICAO transliteration translates the machine readable space character into a <. It should probably not be displayed like this. But that is a visualization issue IMHO.

Read more comments on GitHub >

github_iconTop Results From Across the Web

To use special characters in a column name, enclose the ...
To use special characters in a column name, enclose the entire name in brackets ( [] ) and add a ] to any...
Read more >
How to remove blank spaces and characters in column names?
I'm trying to build a processing script in R which essentially strips all columns of blank spaces and special characters, as these two...
Read more >
Quoting Special Characters
1 Special Characters​​ That could be a problem because blanks and many punctuation characters have special meanings to the command shell, the ...
Read more >
Column names with spaces or other special characters #2243
Various verbs have issues if column names contain spaces or other non-alphanumeric characters. They work only if all column names are valid R...
Read more >
Prevent file import errors caused by special characters or ...
When you import a file of contacts, we recognize characters that are common to email addresses, such as: Capital letters (A - Z) ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found