{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/13f747019ef24913a3f4b880359afb93\" frameborder=\"0\" width=\"1114\" height=\"835\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":835,"width":1114,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":835,"thumbnail_width":1114,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/13f747019ef24913a3f4b880359afb93-23a6c05b80b063a3.gif","duration":101.716,"title":"Persistent Locale Warning During Content Fetching","description":"In this video, I wanted to address a persistent warning we're encountering regarding our SDK integration, specifically about the locale parameter not being correctly provided. Despite passing the locale as a top-level parameter and seeing it logged correctly as E-N-U-U-S, we're still receiving the warning. I’ve tested the content in multiple languages, including German and French, and everything appears to render correctly. I’m flagging this issue to see if it’s a misconfiguration on our end or if it might be something else. Any insights or suggestions would be appreciated."}