App becomes unresponsive when it's sent to the background and then brought back to the foreground during playback

Vega Open Beta Bug Reports
1

: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

If the animations are enabled for the navigation then the app becomes unresponsive when it’s sent to the background and then brought back to the foreground during playback. It works fine if the navigation animations are disabled.

App Name:
App Link on Amazon Appstore (found through Developer Console → Actions column in App List → View on 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. Download/Clone the latest vega sample app from - GitHub - AmazonAppDev/vega-video-sample: This sample app shows you how to implement a W3C media player and the core multimedia functionality, such as interactive screens, a video player, search, and focus management.
  2. Open in vscode and modify the navigationOptions to have animationEnabled: true in src/components/navigation/AppStack.tsx
  3. Install dependancies and run the app in the device.
  4. Start any playback, keep it playing for few seconds.
  5. Pause the video and wait for the screensaver to appear (takes 5 mins after pausing)
  6. Once the screensaver is visible click on back button on d-pad to go back to the application
  7. Try to move focus to different components in the details screen.
  8. You can also put the app in background by pressing home button and put it in the foreground by using VLCM, it will behave the same for this case too.

3. Observed Behavior

Explain what actually happened, noting any discrepancies or malfunctions.

The app becomes un-responsive after it is brought to the foreground

4. Expected Behavior

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

The app should remain responsive after it is brought to the foreground

4.a Possible Root Cause & Temporary Workaround

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

It only occurs when `animationEnabled: true` is passed to the `screenOptions` while creating the `Stack.Navigator`, so the issue might be with the navigation libraries. 
Temporary solution is to disable the animations for `Stack.Navigator`

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 Kepler Studio Extension, please share log files from below folders:
     ~/.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: 0.21.4726
  • App State: Foreground
  • OS Information
    Please ssh into the device via kepler exec vda shelland copy the output from cat /etc/os-releaseinto the answer section below. Note, if you don’t have a simulator running or device attached kepler exec vda shell 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="10"
OS_VERSION="1.1"
BRANCH_CODE="TV Ship"
BUILD_DESC="OS 1.1 (TV Ship/4434)"
BUILD_FINGERPRINT="4.0.163721.0(3072cab629675a74)/4434N:user-external/release-keys"
BUILD_VARIANT="user-external"
BUILD_TAGS="release-keys"
BUILD_DATE="Thu Sep 25 15:30:34 UTC 2025"
BUILD_TIMESTAMP="1758814234"
VERSION_NUMBER="1001010443450"

7. Example Code Snippet / Screenshots / Screengrabs

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

// modify `navigationOptions` object inside src/components/navigation/AppStack.tsx to have the following value

  const navigationOptions = {
    headerShown: false,
    animationEnabled: true,
  };

: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.


<!-- Describe your playback issue if applicable -->

Please share the following details in addition:_

  • Player SDK: [Bitmovin, 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.

This issue is reproducible 8 out of 10 times, so please try at-least three times if you are not able to reproduce
3

Hi @Chandraprakash_Sutha,

Thank you for reporting this issue. We will pass on this to the concerned team for further investigation. We will let you know when there is an update.

Regards,
Siva