Xamarin.AzureCommunicationCalling.iOS 2.3.0-beta.1.1

This is a prerelease version of Xamarin.AzureCommunicationCalling.iOS.
There is a newer prerelease version of this package available.
See the version list below for details. 
dotnet add package Xamarin.AzureCommunicationCalling.iOS --version 2.3.0-beta.1.1
NuGet\Install-Package Xamarin.AzureCommunicationCalling.iOS -Version 2.3.0-beta.1.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="Xamarin.AzureCommunicationCalling.iOS" Version="2.3.0-beta.1.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add Xamarin.AzureCommunicationCalling.iOS --version 2.3.0-beta.1.1
#r "nuget: Xamarin.AzureCommunicationCalling.iOS, 2.3.0-beta.1.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install Xamarin.AzureCommunicationCalling.iOS as a Cake Addin
#addin nuget:?package=Xamarin.AzureCommunicationCalling.iOS&version=2.3.0-beta.1.1&prerelease

// Install Xamarin.AzureCommunicationCalling.iOS as a Cake Tool
#tool nuget:?package=Xamarin.AzureCommunicationCalling.iOS&version=2.3.0-beta.1.1&prerelease

Naive binding for Azure Communication Calling SDK for iOS.

This nuget is just a binding library for this native iOS library : https://github.com/Azure/Communication/releases

Product Compatible and additional computed target framework versions.
Xamarin.iOS xamarinios is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

  • Xamarin.iOS 0.0

    • No dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.3.0-beta.4.1 239 1/25/2023
2.3.0-beta.2.1 1,570 11/9/2022
2.3.0-beta.1.1 200 10/12/2022
2.2.2.1 559 1/25/2023
2.2.0.1 1,381 6/21/2022
2.2.0-beta.1.4 665 5/24/2022
2.2.0-beta.1.3 360 3/2/2022
2.2.0-beta.1.2 178 2/21/2022
2.1.0-beta.1.5 206 12/2/2021
1.1.0.4 440 12/2/2021
1.1.0-beta.1.1 246 6/11/2021
1.0.1.4 726 5/13/2021
1.0.0-beta.9.3 270 3/12/2021
1.0.0-beta.9.2 218 3/10/2021
1.0.0-beta.8.2 272 2/10/2021
1.0.0-beta.7.1 190 1/14/2021
1.0.0-beta.6.1 266 12/4/2020
1.0.0-beta.5.1 242 11/21/2020
1.0.0-beta.4.4 273 11/15/2020
1.0.0-beta.4.3 249 11/11/2020
1.0.0-beta.4.2 274 10/29/2020
1.0.0-beta.4.1 284 10/27/2020

Features Added:
Azure Communication Services introduces the concept of a room for developers who are building structured conversations such as virtual appointments or virtual events. Learn more about rooms here. Get started using rooms by following the quick start guides.
Callkit Integration
Application will be able to configure call capabilities with CallKitOptions.
Application will be able to pass the means to reach a call recipient and the display name with CallKitRemoteInfo.
Application will be able to use reportIncomingCallToCallKit to handle notification when the app is in kill state.
Support for stopping an incoming call because it was answered in another device, or caller cancelled, etc.
Dominant Speakers
Dominant speakers is an extended feature that allows you to obtain a list of the active speakers in the call. The dominant speakers list can change dynamically according to the activity of the participants on the call.
       
       Bugs fixed:
Fix for issue when a call with a host would not end if the host leaves the call.
Fix for internal update when Call Id changes in the middle of a call.
Fix for fetching token from background thread blocks the creation of CallAgent.
Fix for simulator crash when UI window size is returned as zero.
Fix for audio not flowing issue when resume ACS call from PSTN call.
Fixed crash when an invalid token is provided.
Fix for wrong response with isMuted() method when user is trying to mute ACS participant.
Fix for issue where local user stops streaming during connecting state, remote participant sees them as rendering stream.