IzioDev / IzioDev/twilio_programmable_voice
Se mettre au point sur les edges cases du plugin
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Les backgrounds edge cases sont décrit dans #13
- [ ] Si la registration de l'access token à fail, essayer de faire remonter l'erreur.
- [ ] Le double appel.
- [ ] Le mute (vérifier des deux côtés).
- [ ] Le hold (vérifier des deux côtés).
- [ ] Si l'un des participants coupe l'appel, vérifier que l'appel est bien terminée.
- [ ] Le haut parleur.
- [ ] Les appareils bluetooth.
- [ ] Des problèmes de réseau pendant l'appel (essayer de mettre un timeout si pas de réseau pendant x secondes).
- [ ] On est en cours d'appel, on appuie sur le bouton home, qu'est-ce qu'il se passe ?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reading the background edge cases in issue #13 and review the Flutter Twilio Voice plugin's current call behavior. Work through the checklist for registration errors, duplicate calls, mute, hold, participants leaving, audio routing, Bluetooth, network loss, and returning home. Done means each listed edge case has defined and verified behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- audio-video-rtc, mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100