- Genesys Cloud Web Messaging SDK v1.24
- React 18 environment
- Custom corporate branding requirements
Could someone explain why the launcher config object in the createWidget call ignores the position and colors properties? I am passing a valid JSON payload with position: 'bottom-right' and custom hex codes, but the widget renders in the default bottom-left with the standard purple theme. I have verified the config is being passed correctly in the console. Is there a specific syntax for overriding these UI elements in the deployment config?
Check your structure for the theme object. The Web Messaging SDK does not accept color overrides at the root level of the config. You must nest them inside theme. Also, launcher position is often overridden by CSS if you inject styles after the widget loads. Ensure your config is passed correctly to createWidget.
{
"environmentId": "your-env-id",
"launcher": {
"position": "bottom-right"
},
"theme": {
"colors": {
"primary": "#0056b3",
"secondary": "#ffffff"
}
}
}
I faced this while integrating with Microsoft Teams tabs. The SDK v1.24 is strict about the schema. If the theme key is missing, it defaults to Genesys purple. Verify your React state isn’t batching updates that drop the config. Use console.log before createWidget to confirm the object structure matches the API spec exactly.