WebPhone needs error catching when a user does not have a 'device' that supports the webphone
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
- Domain
- audio-video-rtc, frontend
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
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
that'd be awesome.
Thanks!
- Dominant language
- TypeScript
- Stars
- 93
- Forks
- 53
- Avg merge
- 7d
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ringcentral/ringcentral-embeddable
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
ringcentral/ringcentral-embeddable#1215 · 3 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ringcentral/ringcentral-embeddable#1214 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
ringcentral/ringcentral-embeddable#1203 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in ringcentral/ringcentral-embeddable
Similar issues
-
comp/dashboard P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#117722 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·