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.
Bug Description
1. Summary
React Native WebView app crashes with SIGABRT in stem-init on every launch. App never reaches foreground. hadCompInFg is always false.
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
-
- Create a new React Native Vega app using
vega project generate --template helloWorld - Install
@amazon-devices/webview ^3.5.7 - Replace App.tsx with a simple WebView component loading a remote URL
- Set runtime-module to
/com.amazon.kepler.runtime.react_native_kepler_2@IReactNativeKepler_0in manifest - Build with
npx react-native build-vega - Install on Fire TV Stick 4K Select with
vega device install-app - Launch with
vega device launch-app
- Create a new React Native Vega app using
3. Observed Behavior
Explain what actually happened, noting any discrepancies or malfunctions.
App crashes with SIGABRT immediately on launch before ever reaching foreground. Key log lines:
ACR_BEGIN COMM:Toolkit!UI SIG:6 P:!usr!bin!stem-init
Failed to open file: liblcm_client.so.0
No power component for app_framework-com.primohoagies.menuboard.main
LCM_PROCESS_ACTIVITY_STATE: inactive
hadCompInFg: false
4. Expected Behavior
Describe what you expected the SDK to do under normal operation.
App should launch, take foreground, and display the WebView loading the remote URL.
4.a Possible Root Cause & Temporary Workaround
Fill out anything you have tried. If you don’t know, N/A is acceptable
stem-init appears to be aborting during sandbox initialization. liblcm_client.so.0 cannot be found in the sandbox. Tried both react_native_kepler_4 and react_native_kepler_2 runtimes — same crash. No workaround found.
5. Logs or crash report
not allowed
6. Environment
Please fill out the fields related to your bug below:
-
- SDK Version: 0.23.8358
- App State: Never reaches Foreground
- Device: Fire TV Stick 4K Select (callie), armv7
- NAME=“OS”|OE_VERSION=“4.0.0”|OS_MAJOR_VERSION=“1”|OS_MINOR_VERSION=“1”|RELEASE_ID=“21”|OS_VERSION=“1.1”|BRANCH_CODE=“TV Ship”|BUILD_DESC=“OS 1.1 (TV Ship/27)”|BUILD_FINGERPRINT=“4.0.344088.0(3072cab629675a74)/27N:user/release-keys”|BUILD_VARIANT=“user”|BUILD_TAGS=“release-keys”|BUILD_DATE=“Thu Jun 18 06:50:08 UTC 2026”|BUILD_TIMESTAMP=“1781765408”|VERSION_NUMBER=“2101010002720”|
7. Example Code Snippet / Screenshots / Screengrabs
Include any relevant code or component setup in React Native that can help reproduce the bug.
import { WebView } from "@amazon-devices/webview";
import React from "react";
import { View, StyleSheet } from "react-native";
export const App = () => {
return (
<View style={styles.container}>
<WebView
hasTVPreferredFocus={true}
source={{ uri: "https://example.com" }}
javaScriptEnabled={true}
domStorageEnabled={true}
/>
</View>
);
};
const styles = StyleSheet.create({
container: { flex: 1 },
});
Manifest:
schema-version = 1
[package]
title = "My App"
version = "1.0.0"
id = "com.example.myapp"
[components]
[[components.interactive]]
id = "com.example.myapp.main"
runtime-module = "/com.amazon.kepler.runtime.react_native_kepler_2@IReactNativeKepler_0"
launch-type = "singleton"
categories = ["com.amazon.category.main"]
[wants]
[[wants.service]]
id = "com.amazon.webview.renderer_service"
[[wants.service]]
id = "com.amazon.gipc.uuid.*"
[offers]
[[offers.service]]
id = "com.amazon.gipc.uuid.*"
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.
Please share the following details in addition:_
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
Q: Are there any special headers required to reproduce the issue you are facing?
N/A
Additionally please provide the following if possible
Provide Screenshots / Screengrabs / Logs. Please include as much information as you can that will help debug.
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.