usePreventHideSplashScreen() is not working, splash screen is hidden right after app starts rendering itself

:warning: Before you continue


Before submitting a bug report, please review our troubleshooting documentation at https://developer.amazon.com/docs/kepler-tv/troubleshoot-overview.html.

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

After updating Kepler device to the latest OS version (201010440450) the splashscreen hides itself right after app starts rendering its content.
I’m using usePreventHideSplashScreen() and useHideSplashScreenCallback() to have a full control over the native splashscreen.

Context: App uses WebView and hideSplashScreen callback is called when WebView.onLoad handler is called.

App Name: U
App Link on Amazon Appstore (found through Developer Console → Actions column in App List → View on Amazon.com): U: TV Series Stream on Demand - App on Amazon Appstore

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. Follow the example from https://developer.amazon.com/docs/kepler-tv-rn/0.72/splashscreenmanager.html

3. Observed Behavior

Explain what actually happened, noting any discrepancies or malfunctions.

Splashscreen is hidden when the app starts rendering itself. It looks like `usePreventHideSplashScreen()` is not working.

4. Expected Behavior

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

Splashscreen should remain visible after calling `usePreventHideSplashScreen()` until `useHideSplashScreenCallback` callback is executed.

4.a Possible Root Cause & Temporary Workaround

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

<!-- Answer here -->

5. Logs or crash report

(Please make sure to provide relevant logs as attachment and share VPKG file with your Amazon contact)

For crash issues, please refer this guide for faster troubleshooting: https://developer.amazon.com/docs/kepler-tv/detect-crash.html.

  • 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.20.3154
  • 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
    callie:/$ cat /etc/os-release
    NAME="OS"
    OE_VERSION="4.0.0"
    OS_MAJOR_VERSION="1"
    OS_MINOR_VERSION="1"
    RELEASE_ID="2"
    OS_VERSION="1.1"
    BRANCH_CODE="VegaMainlineTvIntegration"
    BUILD_DESC="OS 1.1 (VegaMainlineTvIntegration/4404)"
    BUILD_FINGERPRINT="4.0.140921.0(3072cab629675a74)/4404N:user-external/release-keys"
    BUILD_VARIANT="user-external"
    BUILD_TAGS="release-keys"
    BUILD_DATE="Thu Jul 31 19:48:28 UTC 2025"
    BUILD_TIMESTAMP="1753991308"
    VERSION_NUMBER="201010440450"
    

7. Example Code Snippet / Screenshots / Screengrabs

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

https://developer.amazon.com/docs/kepler-tv-rn/0.72/splashscreenmanager.html

: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 @Adrian

Sorry for the delayed response.

Our team is working on this and will keep you updated.

Thanks,
Rohit