[iOS AzureCommunicationCalling 1.0.1] Call state return .none when the network is intermittent and call end has no callback for the first tap
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, ios
- Domain
- audio-video-rtc, mobile, networking
Research direction
Start by reproducing the airplane-mode sequence with AzureCommunicationCalling 1.0.1, observing call state, endCallReason, and the callback from call.hangUp. Done means an interrupted connection reports .disconnected with a network-related endCallReason, and the first hangUp call produces its callback.
Written by the indexing model from the issue text.
Description
Describe the bug
The call state would return .none after the internet connection is interrupted for 1 minutes.
To Reproduce
Steps to reproduce the behavior:
- Join a call successfully with good network condition
- call state return .connected
- Open airplane mode for more than 1 minutes
- call state return .none
- end the call by
call.hangUp - There is no callback for the first call hangUp. If you call
hangUpagain, it would have a callback
Expected behavior
When the network is interrupted, the callState should return .disconnected rather than none. And the endCallReason should indicate it's because of network issue
Screenshots
- Version [1.0.1]
Logs
Log file:
No Internet State.xcappdata.zip
- 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 · 1 comment ·
-
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