WebPhone needs error catching when a user does not have a 'device' that supports the webphone

Open
#1,102 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript

Research direction

No file or test is named. Start by reproducing an account with an extension and login but no device allowed for the webphone, then trace the embeddable's handling of that failure. Done means this condition is caught and surfaced with a useful message instead of the generic error.

Written by the indexing model from the issue text.

Description

enhancement

We had a user who had been linked to the wrong 'phone' in the devices. It was removed, but we forgot to put back another 'device' for them. So they had an extension, and a login, and an account etc, but no device that was 'allowed' for the webphone.

This error was not trapped correctly by the webphone and send me on a bit of a goose chase trying to understand what had gone wrong.

If you have some way to get this information from within the embeddable and surface the issue rather than the generic

Image

that'd be awesome.

Thanks!

Dominant language
TypeScript
Stars
93
Forks
53
Avg merge
7d
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ringcentral/ringcentral-embeddable

All issues in ringcentral/ringcentral-embeddable

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.