[Android] - on internet disconnect, calling SDK triggers "NONE" state
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- android, azure
- Domain
- audio-video-rtc, mobile
Research direction
Start by reproducing the issue on Android API 30 with azure-communication-calling 1.2.0-beta.2: begin a call, disconnect the internet, and observe the OnCallState "NONE" event with code 410. Check the behavior of call.hangUp after disconnect; done means the expected disconnect behavior and whether hangUp should produce a usable state transition are established.
Written by the indexing model from the issue text.
Description
Describe the bug
During ongoing call if network on Android device is disconnected, OnCallState change receives "NONE" event with 410.
After this, the call to call.hangUp does nothing, so user can not exit application.
Questions:
Please guide about the expected behaviour on network disconnect. can application expect disconnected state when network is disconnected?
on internet disconnect call.hangUp does nothing, no state change received? is it a bug
To Reproduce
Steps to reproduce the behavior:
- start a call
- disconnect internet
Desktop (please complete the following information):
- OS: Android API 30 Pixel 4
com.azure.android:azure-communication-calling:1.2.0-beta.2
https://skype.visualstudio.com/SPOOL/_workitems/edit/2582183
- Dominant language
- No language data
- Stars
- 340
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
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.
More from Azure/Communication
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure/Communication#600 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/Communication#599 · 4 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Azure/Communication#598 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/Communication#543 ·
-
Needs: triage :mag:
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/Communication#447 ·
All issues in Azure/Communication
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
QwenLM/Qwen-MM-Plugins#70 ·
-
area: tools priority: p3 status: needs review type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
use-agent-os/agent-os#3162 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
home-assistant/core#182762 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100