[iOS AzureCommunicationCalling 1.0.1] The callClient.createCallAgent block main thread if the network is poor or not connected
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- swift
- Domain
- mobile-dev
Research direction
Start at the AzureCommunicationCalling iOS 1.0.1 callClient.createCallAgent entry point and reproduce the behavior with the device offline, including when called from DispatchQueue.main.async. Check whether the completion callback is delivered with an error and whether the main thread remains unblocked; done means the failure is reported through the callback without blocking.
Written by the indexing model from the issue text.
Description
Describe the bug
Call the function blow when there is no Internet connection, there wouldn't have any call back and block the whole main thread if I make the call inside DispatchQueue.main.async
callClient?.createCallAgent(userCredential: tokenCredential, options: options) { [weak self] (agent, error) in
}
To Reproduce
Steps to reproduce the behavior:
- Close the internet connection in your device
- Try to create connection with
callClient?.createCallAgent - There wouldn't have any callback to indicate the connection is failed
Expected behavior
There should have a callBack with an error indicate the connection failed.
Screenshots
If applicable, add screenshots to help explain your problem.
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
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
client-controller-update ta-bot-triage team-money-movement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36594 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mozilla-mobile/firefox-ios#35743 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
hemilabs/ui-monorepo#2323 ·
-
Needs: Author Feedback Needs: Repro
Difficulty 1/5 Under an hour Newbie friendliness 92/100
react/react-native#58621 · 1 comment ·