Screen Share not working with Azure Communication iOS SDK

Question

I'm currently working on integrating the Communication SDK into my iOS app and have encountered two challenges:

Establishing a connection between two participants has proven to be problematic. Despite my efforts, I have not been successful in achieving this connection.

1. Another obstacle I've encountered is the inability to find a method for screen sharing when the app is in both the foreground and background states. I've thoroughly searched through the documentation, including the provided link (https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/voice-video-calling/get-started-with-video-calling?pivots=platform-ios), but haven't found any relevant information.

I've utilized the following SDK for implementation: https://github.com/Azure-Samples/communication-services-ios-quickstarts.

If anyone has insights or suggestions on overcoming these challenges, or if there are undocumented features related to screen sharing with the Azure Communication SDK for iOS, your assistance would be greatly appreciated.

Answer 1

Hello @Saurav Sinha sorry to hear you're facing these challenges.

To answer your first question, can you please share specific error message(s) you are getting when trying to establish a connection?

In the meantime, make sure the user access tokens being used are valid and have not expired. Invalid tokens will cause connection failures. The access tokens expire after 24 hours by default. You can check the expire claim in the token payload to see the expiration time.

Also, if you are caching or persisting tokens, make sure to renew them so you always use a non-expired one. The SDKs will throw errors if an expired token is passed. Review the authentication best practices which include token validation

Regarding your second question, the answer is no. Currently there is not a built-in way to share the screen while in a background app state on iOS. However, I will reach out to the ACS engineering team to see if there is a sharable workaround and get back to you.