Hi everyone,
We are experiencing a critical issue with our Messaging for In-App and Web (MIAW) / Embedded Service Deployment failing to load specifically when the user's browser language is set to French (fr / fr-CA).
Everything functions perfectly when tested in English browser (both English and French User). However, when switching the browser language to French, the chat window fails to mount the pre-chat form, leading to a blank screen with no specific error in console both for English and French User.
Native Setup Test Window Reproduction: This issue reproduces out-of-the-box inside the native Salesforce Setup Test Window when the browser language is changed to French. This confirms the defect is independent of our custom Visualforce page or custom code.
Configurations Already Verified & Implemented:
1. Embedded Service Deployment Settings: French (fr / fr-CA) is explicitly added, active, and published under the deployment settings.
2. Experience Cloud / Site Languages: French is enabled and active under Digital Experience Site Settings, and the site has been fully Published.
3. Custom Labels & Translation Workbench: All standard and custom pre-chat form field labels, button text, and instructions have active, fully mapped French translations saved.
4. Code Snippet Locale Mapping: Dynamic language mapping (embeddedservice_bootstrap.settings.language = userLang;) and useHostSiteLanguage = true have been verified.
5. Testing Variations: We have tested toggling pre-chat forms on/off and forcing deployment republishes without resolution.
Has anyone encountered this specific CDN package / localized component initialization crash for non-English locales in Enhanced Chat? Any insights on backend CDN bundle compilation or missing metadata flags for fr locales would be greatly appreciated!
Thanks in advance for your help!
Hi Seema, since it also fails in the Salesforce test window, I'd lean toward a Salesforce-side issue rather than your code. Have you tried testing fr-FR and fr-CA separately? I'd also open a Salesforce Support case with the deployment ID and browser details. You've already ruled out most of the usual configuration issues.
