App Crash : App coming on foreground from background while the ShareVideoUnit is on the view

Meeting SDK Android
1

Description
App crashes when a shareVideoUnit is on the screen (to reproduce : app goes to the background and returns to foreground) i.e on onResume with the following exception:

image
image1006×425 91 KB

Which Android Meeting SDK version?
5.7.1.1267

To Reproduce(If applicable)
Steps to reproduce the behavior:

  1. Make sure a shareVideoUnit is active on the screen
  2. Make the app go background, open another app our app being in the background
  3. Return to our app
  4. See error

Smartphone (please complete the following information):

  • Device: Pixel 5
  • OS: Android 11
2

Hi @ashutosh.singh, thanks for the post.

Sorry to hear you’re running into this crash. Are you able to reproduce this in the SDK sample app? Also, can you please elaborate around what you mean when you say “Make sure a shareVideoUnit is active on the screen”? Does this mean that the share view is being used to share content, or just present and inflated in the layout?

Thanks!

3

Thank you for the response @jon.lieblich

I was not able to reproduce it on the SDK sample app.

The share view is present inflated in the layout and is actively rendering a screen share of another user (who are using other zoom clients, the app does not support sharing content here)

4

Hi @ashutosh.singh,

Can you please provide some context around your implementation? How exactly are you displaying the shared content in your app?

Thanks!

5

I’m using a frame layout inflating a Custom view whose main view is a MobileRTCVideoView inside a parent of FrameLayout, in a similar manner as implemented in the sample app.

using renderInfo as MobileRTCRenderInfo(0, 0, 100, 100) if that matters.

Can you please explain to me what does that error relates to the implementation and what can be looked into to find a solution fast? As this a production issue and needs urgent resolution.

6

Hi @ashutosh.singh,

Can you please provide more information, including all code snippets related to your implementation of this view? Currently, we do not have enough information to determine why this is happening since it is not reproducible in the sample app.

Thanks!

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.