Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better error handling and retries #28

Open
mdwelsh opened this issue Dec 8, 2023 · 0 comments
Open

Better error handling and retries #28

mdwelsh opened this issue Dec 8, 2023 · 0 comments

Comments

@mdwelsh
Copy link
Contributor

mdwelsh commented Dec 8, 2023

We need to do a better job on the client at dealing with various kinds of errors and timeouts.

  • If a conversation never gets started after calling .start(), we should proactively stop it and reconnect. This would be a workaround for Sometimes call never transitions out of "idle" state #25.

  • If the Websocket connection fails, we need to deal with that and retry a few times, showing an error page if the error is persistent. The challenge here is that this is currently managed internally by the VoiceSession and the app does not have visibility into the connection state. We should migrate .warmup() out of the constructor so it can use the onerror signal that the client sets up for this, be sure we're catching errors on .warmup() and calling .onerror when they do happen, and probably also expose the connection state (not just the live conversation state) as part of the VoiceSession.state field.

  • CallCharacter should transition to an error page if it gets an error and retries aren't working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant