Skip to content

Create ui-c8y-1023-4-1-make-sure-language-is-actually-supported-10376.md #3947

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.

Sign up for GitHub

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

Merged
reey merged 4 commits into from
Dec 1, 2025
Merged

Create ui-c8y-1023-4-1-make-sure-language-is-actually-supported-10376.md #3947

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
22f9940
Commited new change note
c8y-ui-change-log-publisher[bot] Nov 25, 2025
7ef8c02
Apply suggestions from code review
reey Nov 25, 2025
3677043
Apply suggestions from code review
reey Nov 25, 2025
50c1a9b
Update content/change-logs/application-enablement/ui-c8y-1023-4-1-mak…
BeateRixen Dec 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions ...on-enablement/ui-c8y-1023-4-1-make-sure-language-is-actually-supported-10376.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
date: ""
title: "Prevent blank screen when preferred language is stored in an invalid format"
product_area: Application enablement & solutions
change_type:
- value: change-VSkj2iV9m
label: Fix
component:
- value: component-YbYJ3gLU_
label: Web SDK
build_artifact:
- value: tc-pjJiURv9Y
label: ui-c8y
ticket: MTM-65299
version: 1023.4.1
---
In some cases, the user's preferred language was stored in an unexpected format in the user object (as an object instead of a string). The UI implementation expected a string and couldn't handle an object. As a result, initializing of the UI application failed, and the user ended up on a blank screen.

This behavior has been adjusted and the application will initialize in these cases as expected.