-
Notifications
You must be signed in to change notification settings - Fork 96
Instructions to install AzureCommunicationCalling without Cocoapods #2016
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @dorjeozer, Can you give more details on what kind of issues are you facing? Errors you are seeing and so on? |
I think the following line of code (from the example project) and the related error will describe the problem I'm having quite well:
error: Cannot assign value of type 'AzureCommunicationCommon.PhoneNumberIdentifier' to type 'AzureCommunicationCalling.PhoneNumberIdentifier' I have generated Common XCFramework using this tool. |
Thank you for following up with this, can you please share a sample project that repros this? Something small and self contained with less code as possible and with the xcframeworks embedded in it. |
Here's an example project where the code is from your tutorial and contains both of the frameworks embedded in: ACSLibraryUI.zip |
Hi, Can you share details on how you are building AzureCommunicationCommon xcframework? Also, make sure you are building version 1.2.0. Can you try using this |
The code works with your file. Would it be possible to get the instructions how it's supposed to be built? Even better would be to get the xcframework available to download for each release. |
Re-assigning this to @mjafferi-msft who owns common SDK |
In the Quickstart guide is a section "Using XCFramework directly". It's quite easy to create a XCFramework out of AzureCommunicationCommon but it has turned out to be a very difficult task to make these two frameworks linked together.
Describe the solution you'd like
It would be great if there was an example project available to understand how this solution can be implemented.
The text was updated successfully, but these errors were encountered: