Playback blacks out when nested modals are open on certain device models

:warning: Before you continue


Before submitting a bug report, please review our troubleshooting documentation at Troubleshoot Issues | Vega Troubleshooting

If you still want to file a bug report, please make sure to fill in all the details below and provide the necessary information.

NOTE: PLEASE ONLY REPORT A SINGLE BUG USING THIS TEMPLATE.
If you’re experiencing multiple issues, please file a separate report for each.


:backhand_index_pointing_right: Bug Description


1. Summary

Playback blacks out if nested Modals are open, on specific device models only. Audio continues playing. Affected devices we found: LG Monitor 34UC98-W, LG TV 43LM5700PUA.

We use nested modals for context menus. We apply an opacity layer over the playback when menus are open, but the behavior persists if we remove this layer.

Issue can be observed in the current App Store version.

App Name: Fubo
App Link on Amazon Appstore (found through Developer Console → Actions column in App List → View on Amazon.com): Amazon.com

Bug Severity
Select one that applies

  • Impacts operation of app
  • Blocks current development
  • Improvement suggestion
  • Issue with documentation (If selected, please share the doc link and describe the issue)
  • Other

2. Steps to Reproduce

  1. Install Fubo from the app store
  2. Start Playback
  3. Press the Gears icon button at the right end of the player interface
  4. In the menu, select Video Quality to open the nested menu.

3. Observed Behavior

Explain what actually happened, noting any discrepancies or malfunctions.

On affected device model, video turns black. Audio continues to play

4. Expected Behavior

Describe what you expected the SDK to do under normal operation.

Video playback remains visible

4.a Possible Root Cause & Temporary Workaround

Fill out anything you have tried. If you don’t know, N/A is acceptable

HDCP related possibly

5. Logs or crash report

(Please make sure to provide relevant logs as attachment)

For crash issues, please refer this guide for faster troubleshooting: Detect Where the App Crash Originates | Design and Develop Vega Apps

  • App/Device Logs

  • Crash Logs

  • Crash Report

  • For issues with Vega Studio Extension, please share log files from below folders:
    For v0.22+:

    ~/.vscode/extensions/amazon.vega-extension-<version>/ExtensionLogs
    ~/.vscode/extensions/amazon.vega-ui-extension-<version>/ExtensionLogs
    

    For v0.21 and earlier:

     ~/.vscode/extensions/amazon.kepler-extension-<version>/ExtensionLogs
     ~/.vscode/extensions/amazon.kepler-ui-extension-<version>/ExtensionLogs
    

6. Environment

Please fill out the fields related to your bug below:

  • SDK Version: Run vega --version (v0.22+) or kepler --version (v0.21 and earlier) and paste output

Active SDK Version: 0.22.6150

Vega CLI Version: 1.2.18

  • App State: Foreground

  • OS Information: Please ssh into the device via vega exec vda shell (or kepler exec vda shell for v0.21 and earlier) and copy the output from cat /etc/os-release into the answer section below. Note, if you don’t have a simulator running or device attached, the command will respond with vda: no devices/emulators found

    NAME="OS"
    OE_VERSION="4.0.0"
    OS_MAJOR_VERSION="1"
    OS_MINOR_VERSION="1"
    RELEASE_ID="14"
    OS_VERSION="1.1"
    BRANCH_CODE="TV Ship day60"
    BUILD_DESC="OS 1.1 (TV Ship day60/102)"
    BUILD_FINGERPRINT="4.0.253712.0(3072cab629675a74)/102N:user/release-keys"
    BUILD_VARIANT="user"
    BUILD_TAGS="release-keys"
    BUILD_DATE="Fri Mar 20 21:10:28 UTC 2026"
    BUILD_TIMESTAMP="1774041028"
    VERSION_NUMBER="1401010010220"
    

7. Example Code Snippet / Screenshots / Screengrabs

Include any relevant code or component setup in React Native that can help reproduce the bug.

import { ExampleComponent } from 'custom-sdk';

<ExampleComponent config={{ key: 'value' }} />

:backhand_index_pointing_right: Playback Issues


If this is a playback issue, please provide your content URL, any pre-conditions (like geo-location), and let us know if it’s x86 or arm7.


Affects all content

Please share the following details in addition:_

  • Player SDK: Shaka
  • Player SDK Version: [e.g. 1.23]
    • Audio Codecs: [AAC, ...]
    • Video Codecs: [h.264, mp4]
    • Manifest Types: [m3u8, dash, etc ..]

Q: If applicable, please provide your media/content url
If this is created dynamically, tokenized, etc please provide a way for us to access it

[N/A or Content / Media Url for testing]

Q: Are there any special headers required to reproduce the issue you are facing?

[N/A or Insert Headers]

Additionally please provide the following if possible
Provide Screenshots / Screengrabs / Logs. Please include as much information as you can that will help debug.

<!-- Answer here if applicable --> 

:backhand_index_pointing_right: Additional Context


Any Additional Context you would like to provide?
Add any other relevant information, such as recent updates to the SDK, dependencies, or device OS that may affect the bug.

<!-- Answer here if applicable  --> 

Hi @anthony3662 ,

Thank you for the detailed bug report on the playback blackout issue with nested modals.

Our team is investigating this issue and will provide an update as soon as we have more information. Your mention of HDCP as a possible root cause is noted - we’ll look into whether the modal layering is triggering a content protection renegotiation on those specific panels.

A few clarifying questions:

  • Is the blackout recoverable (e.g., closing the modal restores video), or does it persist until playback is restarted?

  • Does this occur with all content, or only DRM-protected streams?

Thanks for helping us improve the Vega platform.

Warm regards,
Aishwarya

  • Is the blackout recoverable (e.g., closing the modal restores video), or does it persist until playback is restarted?

    • Yes, closing modal restores video
  • Does this occur with all content, or only DRM-protected streams?

    • Both DRM and non-DRM, live streams and VODs

Hi @anthony3662 ,

Thank you for your patience and the additional details.

Our team attempted to reproduce this issue on available LG TV hardware but was unable to trigger the video blackout. This is likely because the specific panel models you mentioned were not available in our test environment.

To help us investigate further, could you please capture and share device logs while the issue is occurring?

This will help us identify what’s happening at the system level when the blackout is triggered by the nested modal.

Warm regards,
Aishwarya

Can you please try the oldest LG TV you have available, or old TVs from other brands? The models we had issues with are over 7 years old.

Thanks!

Just tested on a Vizio D50u-D1 and was observed the issue. I think it’s from 2016.

Hi @anthony3662,

Thanks for testing on the Vizio D50u-D1. We’ve been unable to reproduce on our available hardware (TV Model : LG 43 (43UR7500PSC))- the oldest models we have are still newer than what you’re seeing this on.

Could you please share device logs captured while the blackout is occurring? The logs will help us identify whether this is related to display compositing, HDCP renegotiation, or another system-level behavior on older hardware.

Thanks for your patience.

Warm regards,
Aishwarya

kepler.log (392.0 KB)

Here’s what I got from loggingctl when the issue was happening.

Also, a coworker just tested this on a 2019 Vizio, model V436-G1, and observed the issue.

Hi @anthony3662 ,

Thank you for sharing the logs and for confirming the issue on the Vizio V436-G1 as well.

After reviewing the log file you provided, we noticed it only contains application-level logs. To diagnose this issue, we need unfiltered OS-level logs that capture what’s happening with system components (display compositing, HDCP, etc.) during the blackout.

Could you please recapture logs without any filtering applied? Specifically, we need the full output - including OS/system-level entries - while the blackout is actively occurring.

This will help us pinpoint whether the issue is related to display compositing, HDCP renegotiation, or another system-level behavior on older hardware.

Thanks for your patience.

Warm regards,
Aishwarya

kepler.log (651.5 KB)

Hoping this helps. I captured this using `loggingctl log -f`

We just found the issue on a 2022 Hisense, model 40A35HUV. It’s the newest TV we’ve seen it on so far.