Crashes report themselves. Testers shake the phone. Users tap Report. Each one reaches you with the replay, console, network and device, from phones, the web and TV.
On TV: Apple TV · Android TV · Fire TV · Roku · Samsung Tizen · LG webOS
Same report, whichever way it came in.
Caught automatically. Nobody had to report it.
Download of "low-orbit" failed: Cannot read property 'freeBytes' of undefined
Filed with a shake on a linked test phone.
New capture from Steve
Sent from the app, with the problem circled.
Neon Saints poster never loads
Before the report
Every tap, remote press, screen and log goes into a rolling buffer on the device as it happens. Nothing leaves it until someone reports.
The same trail is recorded on every platform:
When it crashes
The same SDK is also your crash and error monitor. Uncaught exceptions and crashes, including native crashes on iOS and tvOS and ANRs and low-memory kills on Android, are captured without anyone pressing a button, mapped to your source once your build uploads its symbols, and grouped by cause. Each one keeps its trail and device, and on the web a fixed error that comes back in a later release can reopen as regressed.
While you test
Link a test phone or TV to yourself once. From then on, a shake, or holding Play/Pause on the remote, files a private draft with the screenshot, replay and logs. You title it on the dashboard and keep testing. Your users’ release builds don’t change.
1 Link it once
Do the gesture on the device, then click the number it shows. Nothing links until you do.
2 Shake, or hold Play/Pause
No form on the device. On TVs the gesture is yours to change, recorded from a real remote.
3 Title it on the dashboard
Or link a shared QA device to the team, and its captures land in the inbox for anyone to file.
Phones and tablets, Android TV, Apple TV and Vega OS. In a simulator or emulator, press Shift+B. How linking works
When a user reports
The screenshot is taken before the reporter opens. Users circle what’s wrong and say what they expected.
Try it. Press Report a bug, click the screenshot to circle the empty Neon Saints poster, give it a title and send.
On send
Each report lands with its replay beside the trail. Five devices, five real reports.
WEBNeon Saints poster never loads
IPHONEDownload fails on Low Orbit
ANDROIDKitchen at Midnight freezes on buffering
APPLE TVSubtitles run 2 seconds late in Paper Fleet
ANDROID TVNeon Saints poster is blank
On arrival
A summary, a suggested priority and similar reports, the moment it lands. You make the call.
Same day
Assign, schedule and discuss. TV, phone and web bugs move through the same columns.
Eight SDKs, one report format. Pick yours.
// npm
npm i @everframe/react // SPM
.package(url: "github.com/scriptx-com/everframe" // Maven
implementation "dev.everframe:core:$everframeVersion"
implementation "dev.everframe:reporter-ui:$everframeVersion" // npm
npm i @everframe/react-native // pub.dev
flutter pub add everframe_flutter // Maven Central
implementation("dev.everframe:kmp:1.2.1") // npm
npm i -D @everframe/roku // npm · or a <script type="module"> tag
npm i @everframe/web Crash monitoring, QA capture and in-app bug reports usually mean two or three tools. Everframe is one SDK for all three, on phones, the web and TV.
A half mark means partial or a paid add-on. This reflects what Everframe focuses on, not a feature-for-feature audit: Sentry and Bugsnag go deeper on error monitoring. Everframe puts crashes, tester captures and user reports in one place, each with the evidence attached.
Free for 1,000 monthly active installs. Starter is $19 a month when you go to production.