Skip to content

Conversation controls should no-op or expose capability state when disconnected #678

@kalvin807

Description

@kalvin807

Why

  1. App code had to wrap sendUserActivity() behind status === "connected" checks.
  2. setMicMuted is failing in text-only conversations. App code had to check if a conversation is going to be voice or text before starting a conversation

What

  1. make calls like sendUserActivity() safely no-op when no active conversation exists
  2. make micMuted and setMuted() should be harmless in text-only mode

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions