Skip to content
Everframe
Sign inGet started →
Vega OS SDK · Preview: JavaScript errors only

Vega OS errors, reported in preview.

JavaScript crash and error reports from your Vega OS apps, stored across the crash and mapped back to your source. A preview.

Get started → See a real report

The Vega OS SDK is a JavaScript-only preview for React Native for Vega apps. It reports uncaught errors, unhandled promise rejections and the errors you pass to it. A crash is written to storage before the app stops and sent on the next launch if it could not be sent first. A linked Vega OS device files a quick capture when you hold Play/Pause.

JavaScript errorsquick capturerelease healthpromise rejectionsmapped stack framesbreadcrumbsdevice

JavaScript crash reporting for Vega OS apps

How Vega OS compares with Roku, Apple TV and Android TV as a React Native target is covered in React Native on Roku: why it can’t, and what teams ship instead.

Vega OS apps are written in React Native for Vega, on React Native 0.72. The Everframe Vega OS SDK is plain JavaScript: install @everframe/vega, call init() at the top of index.js and pass the AsyncStorage Vega OS ships. Uncaught errors, promise rejections still unhandled after about two seconds, and errors you pass to captureException become reports in the same shape as every other platform’s.

A preview, with stated limits

It reports JavaScript errors only. Crashes in native or C++ code, Hermes engine aborts, ANRs and watchdog kills never reach JavaScript, so it cannot see them; Vega OS records those in its own crash reports. There is no reporter, screenshot or session replay on Vega OS yet. The SDK is verified on Vega OS 1.1; React Native 0.83 on Vega OS 1.2 is untested. See the Vega OS docs for the full list.

Quick capture from a linked device

A teammate’s Vega OS device can file quick captures with the remote, the same way phones and other TVs do. Link it under Project settings → Devices, then hold Play/Pause for about 1.5 seconds: a draft with the breadcrumbs and the device, app and user details lands in the dashboard, where you title it. There is no screenshot or replay, since the SDK is JavaScript only, and the long press also reaches your app, so it typically toggles playback once. It needs no code beyond init(). See Quick capture on real devices.

Release health for JavaScript crashes

With an explicit app version, the SDK records foreground sessions and links fatal JavaScript errors to the session that crashed. Release health shows crash-free session rates by version, with alerts when a release falls below your target. Caught errors and promise rejections remain error reports. Native crashes and OS kills are outside this coverage; sessions without a completion or a matching JavaScript fatal stay unknown. Debug builds do not collect health. See configuration and coverage.

Readable stack traces

The Vega OS build names each bundle by its content hash, and every report carries that name. Upload the source map after each release build with npx @everframe/cli sourcemaps upload-vega, and frames are mapped to your files, functions and lines.

Fire TV on Fire OS

Fire TV apps on Fire OS use the Android SDK, with crash and error reporting and session replay. See Fire TV.

What every Vega OS report carries

  • The error — exception type, message and the JavaScript stack, mapped to your source files once the build's source map is uploaded.
  • Whether it ended the app, and whether it was an uncaught error, a promise rejection or one you reported.
  • The breadcrumbs you added, and the user if your app set one.
  • App version and build, the bundle the error came from, screen size, locale and time zone.

Install

npm install @everframe/vega

Questions

Is Vega OS fully supported?

No, it is a preview, and it reports JavaScript errors only. Native and C++ crashes, Hermes engine aborts, ANRs and watchdog kills never reach JavaScript; Vega OS records them in its own crash reports. There is no in-app reporter, screenshot or session replay on Vega OS.

Can testers file a bug from a Vega OS device?

Yes, with quick capture. Link the device under Project settings → Devices in the dashboard, then hold Play/Pause on the remote for about 1.5 seconds. The draft has the breadcrumbs and the device, app and user details, but no screenshot or replay, and you title it on the dashboard. Your users see no change.

Can I use the React Native SDK in a Vega OS app?

No. It needs React Native 0.84 or later and its own native module, and Vega OS apps build on React Native 0.72 without that module. Vega OS apps use the separate Vega OS SDK, @everframe/vega, which is plain JavaScript.

What happens to a crash?

The SDK writes the report to storage before the app stops, holds the crash for up to 1.5 seconds while it tries to send it, and sends it on the next launch if it could not. A report sent twice is stored once.

Do I get readable stack traces?

Yes, once you upload the source map of each release build with npx @everframe/cli sourcemaps upload-vega. Each report names the bundle it came from, so the right map is used automatically.

Which Vega OS versions are supported?

The preview is verified on Vega OS 1.1, which runs React Native 0.72 and Hermes 0.12. React Native 0.83 on Vega OS 1.2 is untested.

Is Fire TV supported?

Fire TV apps on Fire OS use the Android SDK, with crash and error reporting and session replay. Vega OS is a separate operating system.