Webinar sharing screen issue still a problem

[tylorschuessele (Tylor)]

Description
Appears to be the same issue as this person had back is 2020

Webinar sharing screen issue

Hello, I’ve noticed an issue in a sharing screen feature implementation for webinars in a custom UI. When some of panelists in a webinar starts sharing their screen an attendee receives notification with userId via onShareActiveUser(long userId) callback. But MobileRTCVideoView shows black screen after adding sharing video unit for user with the useId. The same scenario works fine for common meetings. Is it a bug in SDK? Or am I missing something? Android SDK Version 4.6.21666.0429

As an attendee in a webinar I am unable to view the active screen share of a panelist using the below code.
mDefaultVideoViewMgr.addShareVideoUnit(mCurShareUserId, renderInfo);
It populates the MobileRTCVideoView with a grey screen (similar to what you would see if someone was covering their webcam with a webcam cover).

When i promote the attendee to a panelist the screen share does then work and is fully visible.

On the regular Zoom Android App if I join as an attendee this shared screen is fully visible.

Which Android Meeting SDK version?
Android Meeting SDK v5.7.6.1922

[jon.zoom (Jon)]

Hi @tylorschuessele, thanks for the post.

The post you are referencing seems to have been an issue with the SDK sample app’s implementation. Are you running into this issue within your own implementation or in the SDK sample app?

Thanks!

[tylorschuessele (Tylor)]

I am running into it with my own implementation (I just used the same variable names for convenience).

[jon.zoom (Jon)]

Hi @tylorschuessele,

Thanks for confirming. I was able to reproduce this behavior, so no additional information is needed on your end. I’ll keep you updated as soon as we have any new information.

Thanks!

[jon.zoom (Jon)]

Hi @tylorschuessele,

We have identified a fix for this issue and will be including it in the next SDK release. Please let me know if you are still able to reproduce this behavior after the 5.9.0 release becomes available.

Thanks!