Update libraries Android and iOS

[andersonvieiragomeslopes]

Hello, @tompi

Could you update to the latest two versions of the library? It has new features to use.

iOS: 2.3.0-beta.1 Android: 2.4.0-beta.1

[tompi]

Hey, I updated to the betas now, and published to nuget. Do you need the alphas as well?

Let me know if anything is missing/not working.

P.S. I tried making callclient, callagent and videostreamrenderer transitive, hoping it might help with more eager gc, let me know if you experience strange behaviour!

[andersonvieiragomeslopes]

Thanks @tompi.

In the alpha version of iOS I thought that this would be available here but it's not, I downloaded the library to look and make sure of it, I ended up forgetting to update on the problem and remove this one information. I noticed that screesharing for iOS is available in the following version of iOS 2.4.0-beta.1 which unfortunately is in private preview and we can't make it public due to the NDA, although the documentation is already available, which is strange: (. I finished the screensharing implementation on android but I didn't just send it waiting for iOS, but microsoft takes too long to update cocoapods or simply doesn't update as it should.

I can make all the calls on android and publish perfectly, but on iOS I'm stuck in the final step

lipo -create ./ios-arm64/AzureCommunicationCalling.framework ./ios-x86_64-simulator/AzureCommunicationCalling.framework -ouput AzureCommunictionCalling

Error: fatal error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: can't create temporary output file:

This step prevents me from moving forward, we have things that are possible to use only in closed versions, if it's not so much trouble for you, someday I could record a video with it or check if the iOS connection process is all up to date in the repository at regarding local adjustments in your environment.

[raosanat]

lipo should not be used anymore. Any apps built with lipo frameworks will be rejected by Apple.

[andersonvieiragomeslopes]

Hello @raosanat.

Are you talking about it here ?

Well, I'm not an expert on the subject of links, if you have any step by step on the subject, I'd appreciate it.

In this CommunicationUI Xamarin project I'm also having the same problem, the other steps work fine when generating the ApiDefinitions and StructsAndEnums files.

[raosanat]

thanks for the reference, let me reach out to Joshua for more info on this.

[JoshuaLai]

@andersonvieiragomeslopes at quick glance it looks like you have a spelling mistake in output, not sure if that was you copy and pasting or just you typing it out. Otherwise we can investigate intoyour lipo command not having have the proper output files. We can try first making a copy of the framework somewhere and using that as a temporary file that we can write our output to

cp -a ./ios-x86_64-simulator/AzureCommunicationCalling.framework "${YOUR_OUTPUTFOLDER_HERE}"
lipo -create ./ios-arm64/AzureCommunicationCalling.framework ./ios-x86_64-simulator/AzureCommunicationCalling.framework -output "${YOUR_OUTPUTFOLDER_HERE}/AzureCommunicationCalling.framework/AzureCommunicationCalling"

Try this and let me know if it works

[JoshuaLai]

@andersonvieiragomeslopes If you are having trouble with the Xamarin UI library sample please leave a git issue and we would be happy to help you out there as well

[andersonvieiragomeslopes]

Hello,

Thanks for the help @JoshuaLai @raosanat.

Well, I also have problems with the Xamarin UI library, and it's exactly with this linking step on iOS, there seem to be missing folders or the need to create them, I know that I can also get the files I need using the Xamarin UI library for that. I'm going to open a problem in the Xamarin UI library repository.

@tompi if you have anything to add we can continue here too, both paths are valid for me, the important thing is to be able to make the links and get the fat files on ios.