Hi Tomas,
Since the icon elements and expected pseudo-element content are present, the font returns HTTP 200, and applying a color override makes the icons visible, I would focus on the computed CSS color and style precedence rather than the font file itself.
Recommended fix:
Open the affected page and inspect a missing icon in browser DevTools.
Select its ::before pseudo-element and check the Computed values for color, font-family, and content. Compare them with the same icon in your previously working version.
Since a color override makes the icon visible, identify the CSS rule or inherited theme variable that changed after the Atlas Core upgrade. Check whether the icon color matches or blends into the sidebar background.
Add a custom class to the affected navigation item and define the required icon color in your application's custom SCSS. For example:
.ix-nav-icon-fix::before {
color: #ffffff;
}Replace #ffffff with the appropriate contrasting color for your sidebar theme, and apply the class to the element that actually renders the icon pseudo-element. If DevTools shows that the color is applied to a different element, target that element instead.
Ensure your custom styling is loaded after Atlas Core through App Settings → Theme. Rebuild and run the app, then verify the icons in both light and dark modes if both are supported.
Also, verify that the Siemens UI Module version is compatible with your installed Atlas Core version. The Siemens UI Module's official Marketplace documentation includes version-specific dependencies and migration guidance.
References:
Hope this helps! If you find this answer helpful, please mark it as the accepted answer.