Error when using Ukrainian language- object of type ‘NoneType’ has no len()

[SerhiiMorozov]

Good afternoon, encountered a problem while compiling the form.

In Ukrainian there is an apostrophe, example - звʼязатися
When I use it in the question description and try to make a preview, I get an error - object of type ‘NoneType’ has no len()

I tried using other similar characters - ` ’ ʼ , but nothing helped.

Can you tell me how I can fix this?

[wroos]

Welcome @SerhiiMorozov,
Does it work without any special character? Do you have a valid type defined?
You may try \', please.

You probably know: You can use the Online validator to check your form, during development and before deployment. I don’t have a problem here with звʼязатися.

[SerhiiMorozov]

Thanks for the reply, I found out that it’s not the character, but any text, in any language, that I enter in the “question prompt” field

If there is no text in the “text hint” field, everything is fine

I logged out of the form and checked with the validator, it says this:
[row : 19] Group has no label: {‘name’: ‘group_other’, ‘type’: ‘begin_group’}

after which I tried to go into form editing and it told me:
Failure to upload the form definition:
There is an unnamed translation in your form definition.
Please give a name to all translations in your form.
Use “Manage Translations” option from form landing page.

I went into Manage Translations and updated the translation form.
All fields are green and filled in.

I saved it again and tried to enter the form, the error is still the same:
Failure to upload the form definition:
There is an unnamed translation in your form definition.
Please give a name to all translations in your form.
Use “Manage Translations” option from form landing page.

[wroos]

Does it work without any special character? Do you have a valid type defined?

Maybe, you can go through the Help Center article and the documentation please

• Adding Another Language to your XLSForm — KoboToolbox documentation
• Form Language - ODK Docs

If you use multiple languages:

• All labels and all textual fields, incl. hints, messages, must have a definition (column) for each language.
• Languages must be named incl. the international 2-letter language code, e.g. English (en).
• You should also define required_message and constraint_message in each language, to avoid getting system default messages in English.

@SerhiiMorozov

[row : 19] Group has no label: {‘name’: ‘

This warning is ok, if you don’t want to show the title (label) of this group on the user screen.

[SerhiiMorozov]

Thanks for the help, the problem was that there was one “empty” language in the “Manage Translations”, with no language name or code.

[Kal_Lam]

@SerhiiMorozov, @wroos,