This article discusses the cause and resolution of the following error in the email field validation labels when using the i18n properties during the user sign-up process with the Okta Sign-In Widget.

L10N_ERROR(registration.error.doesNotMatchPattern.custom and registration.error.invalidLoginEmail.custom)

• Okta Identity Engine
• Okta Classic Engine
• Sign In Widget Customizations
• Sign Up Page

Users who register their accounts using the Okta Sign-In widget get an error message in the email field whenever they provide an invalid or incorrect email value. 

The two email labels available for validation messages are: 

1. registration.error.doesNotMatchPattern.custom = Provided value for property '{0}' does not match required pattern
2. registration.error.invalidLoginEmail.custom = '{0}' must be in the form of an email address

But when the labels are updated with custom messages without adding the {0} literals, it leads to L10N_ERROR. For example:

1. registration.error.doesNotMatchPattern.custom = custom do not match pattern
2. registration.error.invalidLoginEmail.custom = Custom Invalid Login Email

Include the {0} value along with the custom message for these labels. Adding the {0} value along with a custom message helps us handle the parameter(Primary email) passed by Okta's backend. Examples:

1. registration.error.doesNotMatchPattern.custom = {0} do not match pattern
2. registration.error.invalidLoginEmail.custom = {0} is invalid.

NOTE: This error can also occur when trying to update other i18n property labels that expect {0} literals. Refer to the i18n properties. 

Related References

• L10n_ERROR Message on Password Expiring Page