voxeet / voxeet-sdk-ios

The Dolby.io Communications SDK for iOS.
https://docs.dolby.io/communications-apis/docs/ios-overview
Other
3 stars 0 forks source link

Screen broadcast does not work with UIScene lifecycle (Xcode 11's default) #18

Closed cardoso closed 1 year ago

cardoso commented 4 years ago

When calling startScreenShare(broadcast:true), nothing shows up, stream remains black, and the callback comes back with this error:

Error Domain=com.voxeet.sdk Code=-2343 "Broadcast picker displayed." UserInfo={NSLocalizedDescription=Broadcast picker displayed.}

And this shows up in the logs afterwards:

[Assert] Error in UIKit client: -[UIWindow setScreen:] should not be called if the client adopts UIScene lifecycle. Call -[UIWindow setWindowScene:] instead.

A workaround is to adopt the old lifecycle, but it's definitely not ideal going forward. It would be better if the SDK could detect the new lifecycle and adopt new methods instead.

VTCoco commented 4 years ago

Hello,

I don't think we could fix this for the moment because this error comes from ReplayKit.framework.

http://openradar.appspot.com/FB7671583

I'm afraid that the solution (for now) is to wait a fix from Apple.

cardoso commented 4 years ago

Thanks @VTCoco . That makes sense.

mohadel92 commented 3 years ago

When calling startScreenShare(broadcast:true), nothing shows up, stream remains black, and the callback comes back with this error:

Error Domain=com.voxeet.sdk Code=-2343 "Broadcast picker displayed." UserInfo={NSLocalizedDescription=Broadcast picker displayed.}

And this shows up in the logs afterwards:

[Assert] Error in UIKit client: -[UIWindow setScreen:] should not be called if the client adopts UIScene lifecycle. Call -[UIWindow setWindowScene:] instead.

A workaround is to adopt the old lifecycle, but it's definitely not ideal going forward. It would be better if the SDK could detect the new lifecycle and adopt new methods instead.

any further details regarding this issue , i was going to implement share screen sdk?

FabienLavocat commented 1 year ago

Closing this issue, if this still happens, please reopen.