Vega WebView apps stopped working after latest OS update

Vega Open Beta Bug Reports
1

:warning: Before you continue

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

Vega WebView apps stopped working after latest OS update

App Name: KidoodleTV, DudePerfect, Victory+
**App Link on Amazon Appstore:
**
V+: amzn1.devportal.mobileapp.78bbbbc994fd46179e278061648170df
DP: amzn1.devportal.mobileapp.314934ac66174faba3c71a4d077ddce3
KTV: amzn1.devportal.mobileapp.fbc73c9adb014ea4a3ba018a3e5b4d20

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. Open application
  2. Observe the app crashing a few seconds after splashcreen appears

3. Observed Behavior

Explain what actually happened, noting any discrepancies or malfunctions.

The app is crashing a few seconds after splashcreen appears

4. Expected Behavior

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

The app should not be crashing a few seconds after splashscreen appears

4.a Possible Root Cause & Temporary Workaround

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

The closest we've got to make it work locally was bump React Native to 0.83 version which is the alpha phase now. Static RN elements work but the WebView bundle does not support Kepler 4 and crashes all the same. 0.72 RN version does not work at all.

5. Logs or crash report



RCTSurfacePresenter::startSurface: Concurrent Renderer is enabled

  SurfaceRegistryBinding::startSurface: Failed to start Surface

  "tv.kidoodle.android.main".

    global.RN$SurfaceRegistry was not installed.

  Transition timed out ... Creating surfaces

  Forcefully terminating process 14026 with reason AppNotResponding

6. Environment

Please fill out the fields related to your bug below:

  • SDK Version: 0.22

  • App State: Foreground

  • OS Information: latest production OS (1.72.0.259799.0)

    <!-- Answer here if applicable -->

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.


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

<!-- Answer here if applicable  -->
3

Hi @Ivan_Kohut,

Welcome to the Amazon Developer Community !!

Thank you for the detailed bug report.
The error global.RN$SurfaceRegistry was not installed suggests a React Native runtime compatibility issue introduced by the latest OS update (1.72.0.259799.0).

A few quick questions to help us investigate:

  1. Which SDK version were these apps built with? You mentioned SDK 0.22 - can you confirm the exact version (e.g., 0.22.xxxx)?
  2. When did the apps last work correctly? What was the previous OS version before the update?
  3. Are these apps using the React Native WebView component (@amazon-devices/react-native-w3cmedia) or a standard HTML WebView?
  4. Which RN version is declared in your app’s manifest/package configuration - 0.72?

I’m testing this on my end and will provide an update shortly.

Warm Regards,
Ivy

5

Hello @Ivan_Kohut

We are investigating this issue on priority.
Meanwhile, could you try a clean install and see if the issue is resolved:

npm cache clean --force 
// clears the global npm cache
npm start -- --reset-cache // clears metro cache
npm run clean // this assumes that you have a "clean" script in your package.json
npm update // pulls the latest version of your app's dependencies

Corresponding commands for Yarn:

yarn cache clean --all
yarn start -- --reset-cache
yarn clean
yarn upgrade

Corresponding commands for PNPM:

pnpm cache delete           # command available from 9.x onwards only
pnpm start --reset-cache
pnpm clean
pnpm update

Warm regards,
Ivy

6

Hi Ivy,

1. Setup: Vega SDK 0.22.6021, OS 1.72.0.259799.0
2.I can’t pull the previous OS version, but the update changed the OS UI significantly.
3.Standard WebView app
4. yes

I ran the cache clean and full dependency reinstall you suggested — it didn’t change anything on its own.

Thanks for your help!

Cheers, Ivan