Short Summary of the Bug
On the eSignet-Go login screens, a validation error message is rendered once and then frozen in whatever language was active when it appeared. If the user switches the UI language while the error is on screen, all other UI text (headings, labels, buttons) updates to the new language, but the already-displayed error message stays in the old language.
Description
Environment:
eSignet-Go — oidc-ui login screen (Login with OTP → UIN/VID field).
Providers: https://esignet-go.esqa.mosip.net (mock), https://esignet-go-sunbird.esqa.mosip.net (mosip), https://esignet-go-mosipid1.esqa.mosip.net (sunbird).
Steps to reproduce (case A — "numbers only" error):
- Open a relying party (e.g.
https://healthservices-go.esqa.mosip.net) → Sign In with eSignet → Login with OTP → UIN/VID.
- With the language set to English, type letters (e.g.
abcd) into the UIN/VID field and blur it to trigger the error UIN/VID must contain numbers only.
- Without editing the field, switch the language to Hindi via the language selector.
Steps to reproduce (case B — "required" error):
- Same screen, language set to Hindi, clear the UIN/VID field and blur it to trigger the required error
यह फ़ील्ड आवश्यक है.
- Without editing the field, switch the language to English.
Expected Behavior:
When the language changes, the visible validation error message re-renders in the newly selected language (like every other string on the screen).
Actual Behavior:
The error text does not re-translate — it remains in the language it was generated in, even though the field label, heading and buttons all switch. Confirmed both directions:
- English error
UIN/VID must contain numbers only stays English after switching the UI to Hindi.
- Hindi error
यह फ़ील्ड आवश्यक है stays Hindi after switching the UI to English.
Likely root cause:
The validation message string is computed and stored at validation time rather than being resolved from an i18n key reactively, so a language change does not recompute it. This affects the field-level validation errors generally (required, numbers-only, and other validators), across the shared oidc-ui, hence all three identity systems.
Attachments / Evidence / Links
Case A — UI switched to Hindi, but the error stays English ("UIN/VID must contain numbers only"):
Case B — UI switched to English, but the error stays Hindi ("यह फ़ील्ड आवश्यक है"):
Short Summary of the Bug
On the eSignet-Go login screens, a validation error message is rendered once and then frozen in whatever language was active when it appeared. If the user switches the UI language while the error is on screen, all other UI text (headings, labels, buttons) updates to the new language, but the already-displayed error message stays in the old language.
Description
Environment:
eSignet-Go —
oidc-uilogin screen (Login with OTP → UIN/VID field).Providers:
https://esignet-go.esqa.mosip.net(mock),https://esignet-go-sunbird.esqa.mosip.net(mosip),https://esignet-go-mosipid1.esqa.mosip.net(sunbird).Steps to reproduce (case A — "numbers only" error):
https://healthservices-go.esqa.mosip.net) → Sign In with eSignet → Login with OTP → UIN/VID.abcd) into the UIN/VID field and blur it to trigger the errorUIN/VID must contain numbers only.Steps to reproduce (case B — "required" error):
यह फ़ील्ड आवश्यक है.Expected Behavior:
When the language changes, the visible validation error message re-renders in the newly selected language (like every other string on the screen).
Actual Behavior:
The error text does not re-translate — it remains in the language it was generated in, even though the field label, heading and buttons all switch. Confirmed both directions:
UIN/VID must contain numbers onlystays English after switching the UI to Hindi.यह फ़ील्ड आवश्यक हैstays Hindi after switching the UI to English.Likely root cause:
The validation message string is computed and stored at validation time rather than being resolved from an i18n key reactively, so a language change does not recompute it. This affects the field-level validation errors generally (required, numbers-only, and other validators), across the shared
oidc-ui, hence all three identity systems.Attachments / Evidence / Links
Case A — UI switched to Hindi, but the error stays English ("UIN/VID must contain numbers only"):
Case B — UI switched to English, but the error stays Hindi ("यह फ़ील्ड आवश्यक है"):
