SIGABRT in stem-init on launch - React Native WebView app crashes before foreground on Vega OS 1.1

Vega Open Beta Bug Reports
4

Hi @Andy_T,

Welcome to the Amazon Developer Community!!

Thank you for the detailed bug report on the SIGABRT crash in stem-init during launch of your React Native WebView app on Vega OS 1.1.

After reviewing your manifest configuration, we’ve identified two issues that are likely causing the crash:

1. Incorrect runtime-module path (primary suspect for the crash)

Your manifest uses:

runtime-module = "/com.amazon.kepler.runtime.react_native_kepler_2@IReactNativeKepler_0"

For React Native 0.72 apps on Vega OS 1.1, the correct runtime-module is:

runtime-module = "/com.amazon.kepler.keplerscript.runtime.loader_2@IKeplerScript_2_0"

The react_native_kepler_X@IReactNativeKepler_0 naming convention is for RN 0.83. When stem-init cannot locate the specified runtime module in the sandbox, it aborts — which aligns with the SIGABRT and liblcm_client.so.0 not found errors you’re seeing.

Reference: Getting Started with Vega Web Apps and Webview

2. Missing required WebView services in manifest.toml

Your [wants] section only declares com.amazon.webview.renderer_service and com.amazon.gipc.uuid.*, but the WebView component requires additional platform services. Here’s the full recommended configuration:

[wants]
[[wants.service]]
id = "com.amazon.webview.renderer_service"

[[wants.service]]
id = "com.amazon.inputmethod.service"

[[wants.service]]
id = "com.amazon.media.server"

[[wants.service]]
id = "com.amazon.mediametrics.service"

[[wants.service]]
id = "com.amazon.mediabuffer.service"

[[wants.service]]
id = "com.amazon.mediatransform.service"

[[wants.service]]
id = "com.amazon.audio.stream"

[[wants.service]]
id = "com.amazon.audio.control"

[[wants.service]]
id = "com.amazon.kepler.ucc.publisher"

[[wants.service]]
id = "com.amazon.gipc.uuid.*"

[offers]
[[offers.service]]
id = "com.amazon.gipc.uuid.*"

Reference: Vega Web App Developer Guide

To resolve:

  1. Change your runtime-module to /com.amazon.kepler.keplerscript.runtime.loader_2@IKeplerScript_2_0
  2. Add the missing services to your [wants] section
  3. Rebuild your app
  4. Reinstall and launch

If the crash persists after these changes, could you please share the following to help us debug further:

  • Device logs - Please capture and share the output of vega device logs while reproducing the crash
  • Crash/core dump files - If any crash reports are generated on the device
  • Full build output - The output from vega device install-app and vega device launch-app commands leading up to the crash

We noticed you mentioned “not allowed” under the Logs section - if you’re facing issues uploading files to the forum, you can paste the relevant log snippets directly in a reply or share them via a linked document.

Thanks for helping us improve the Vega platform!

Warm regards,
Aishwarya