Skip to content

Unsupported language errors silently #241

@mattilajoonas

Description

@mattilajoonas

Hi!

Setting unsupported language overrides in conversation.startSession closes the websocket connection immediately and doesn't throw any errors. I'll add the sent and received websocket messages below, they're the same as at the beginning of a successful session.

The api should error or send an event so that we could fallback to another language or show an error to the end user.

⏫: {"type":"conversation_initiation_client_data","conversation_config_override":{"agent":{"language":"et"},"tts":{},"conversation":{}},"source_info":{"source":"react_sdk","version":"0.6.1"}}
⏬: {"conversation_initiation_metadata_event":{"conversation_id":"conv_id_123","agent_output_audio_format":"pcm_16000","user_input_audio_format":"pcm_16000"},"type":"conversation_initiation_metadata"}

relates a bit to #23

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions