<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Everframe</title><description>Guides on bug reporting and QA for mobile, web and TV apps, Everframe product updates, and SDK and service releases.</description><link>https://everframe.dev/</link><language>en</language><atom:link href="https://everframe.dev/rss.xml" rel="self" type="application/rss+xml"/><item><title>Everframe 1.6.0</title><link>https://everframe.dev/changelog/#v1.6.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v1.6.0</guid><description>Everframe 1.6.0 adds quick capture on real devices. Team members can link a phone or TV to themselves from the dashboard, and the device&apos;s capture gesture then files a private quick-capture draft, as simulators already do. This covers phones, Android TV, Apple TV and Vega. Companion is removed and replaced by device linking, and the default quick capture shortcut is now ⇧B.</description><pubDate>Sat, 24 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 1.5.0</title><link>https://everframe.dev/changelog/#v1.5.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v1.5.0</guid><description>Everframe 1.5.0 changes only the hosted service and dashboard. Simulator and emulator quick capture arrives on the platform side, with per-app hotkey settings, a draft inbox for fast captures, and personal capture tokens. JavaScript source maps can now be up to 256 MiB. React Native crashes from bundles delivered by Hot Updater now symbolicate correctly.</description><pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 1.4.1</title><link>https://everframe.dev/changelog/#v1.4.1</link><guid isPermaLink="true">https://everframe.dev/changelog/#v1.4.1</guid><description>Everframe 1.4.1 is a tools release that adds Try on device. The @everframe/cli package can now upload runnable builds of your app from CI. You can then open a report or error occurrence in the dashboard and reproduce it on a live device that runs a matching build. This release also lifts a 25 MB limit that was rejecting larger build-artifact uploads.</description><pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 1.4.0</title><link>https://everframe.dev/changelog/#v1.4.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v1.4.0</guid><description>Everframe 1.4.0 brings two new kinds of context to React Native iOS and Android reports: the exact source commit behind each build, and typed application state with a history of changes. MCP responses for reports and error groups are now much more compact and informative. Reproduction is available to everyone in the dashboard, and the releases view no longer flags web builds that a newer upload has replaced.</description><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 1.3.0</title><link>https://everframe.dev/changelog/#v1.3.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v1.3.0</guid><description>Everframe 1.3.0 is mainly a release of the hosted service and dashboard. Release health now covers web, TV web runtimes, Flutter and Kotlin Multiplatform, tvOS, native Vega and Roku. Error grouping is now automatic for every platform, with no per-app settings to maintain. Web releases are now identified by their version, and several fixes make issue lists, new-error counts and reporter inboxes more accurate.</description><pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 1.2.0</title><link>https://everframe.dev/changelog/#v1.2.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v1.2.0</guid><description>Everframe 1.2.0 turns crash reporting and release health on by default. Android and iOS/tvOS capture crashes with no extra setup, and crash-free rates are reported for each app version. Releases now create themselves from incoming events, and the errors list and error page are redesigned. The SDK key option is renamed to sdkKey on every platform. The old names still work, so upgrading needs no code changes.</description><pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 1.2.1</title><link>https://everframe.dev/changelog/#v1.2.1</link><guid isPermaLink="true">https://everframe.dev/changelog/#v1.2.1</guid><description>Release 1.2.1 is a service and dashboard release: the SDK changes described here need no code changes in your app. Error pages can now play back the session replay leading up to a handled error. The hosted service can now symbolicate native Apple and Android crashes in production. A new crash-only sessions coverage setting is ready in the dashboard ahead of SDK support.</description><pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 1.1.0</title><link>https://everframe.dev/changelog/#v1.1.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v1.1.0</guid><description>Everframe 1.1.0 makes crash and error data easier to read. The dashboard now shows real stack frames for Flutter errors, source maps match more reliably, larger React Native maps are accepted, and replays of React Native Web sessions show their images again. In the SDKs, the Android reporter recovers cleanly when its Activity is destroyed while it is open, and mobile error reports now include each error&apos;s underlying causes. The hosted MCP server now marks every tool as read-only.</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Try Everframe on a Live Phone or TV in Your Browser</title><link>https://everframe.dev/updates/live-device-demo/</link><guid isPermaLink="true">https://everframe.dev/updates/live-device-demo/</guid><description>Everframe&apos;s demo streams a live iPhone, Android phone, Apple TV and Android TV into the dashboard. File a report from one, then open it in your project.</description><pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 1.0.0</title><link>https://everframe.dev/changelog/#v1.0.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v1.0.0</guid><description>Everframe SDKs now share a stable 1.0.0 release across web, React, React Native, Android, iOS, tvOS, Flutter, Kotlin Multiplatform, Roku, and the identity companion package.</description><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Flutter Bug Reports With a Masked Screenshot and 30 Seconds of Replay</title><link>https://everframe.dev/learn/flutter-bug-report-sdk/</link><guid isPermaLink="true">https://everframe.dev/learn/flutter-bug-report-sdk/</guid><description>We ran the new Everframe Flutter SDK on an Android emulator: a masked screenshot, session replay, a Dart error and a 503, as they arrive in the dashboard.</description><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Kotlin Multiplatform Bug Reporting: One Shared API, Native Capture on Each Host</title><link>https://everframe.dev/learn/kotlin-multiplatform-bug-reporting/</link><guid isPermaLink="true">https://everframe.dev/learn/kotlin-multiplatform-bug-reporting/</guid><description>The Everframe KMP bridge shares reporting calls and leaves capture to the native SDK. We ran it in a Compose host: what shared Kotlin sends and what arrives.</description><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Roku Crash Logs: Capturing BrightScript Crashes After the Channel Is Gone</title><link>https://everframe.dev/learn/roku-crash-logs/</link><guid isPermaLink="true">https://everframe.dev/learn/roku-crash-logs/</guid><description>A crashed Roku channel cannot report anything. How to capture Roku crash logs on the next launch, with a stack, key presses and memory before an OOM kill.</description><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 0.9.0</title><link>https://everframe.dev/changelog/#v0.9.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v0.9.0</guid><description>This release renames the product from TraceItX to Everframe across the hosted service and dashboard. It has no changes to SDK behaviour, and most of the remaining work is internal restructuring with no effect on integrations. Your existing projects, reports and stored data carry over unchanged.</description><pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 0.8.2</title><link>https://everframe.dev/changelog/#v0.8.2</link><guid isPermaLink="true">https://everframe.dev/changelog/#v0.8.2</guid><description>Reports and crashes now arrive with a short, high-resolution window of CPU and memory usage leading up to the failure, while playback sessions stop carrying the idle CPU/memory samples that made long sessions expensive for no benefit. The web and React SDKs now take their report hotkey from the dashboard, and the SDK surface has been simplified so the platforms behave the same way. On the service side, the dashboard gets a full-page report and error workbench, playback sessions are attributed to the person watching, an error-monitoring stack lands with symbolication and release regression detection, and a read-only MCP endpoint lets coding agents pull the evidence for a bug themselves.</description><pubDate>Mon, 21 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 0.8.1</title><link>https://everframe.dev/changelog/#v0.8.1</link><guid isPermaLink="true">https://everframe.dev/changelog/#v0.8.1</guid><description>Release 0.8.1 is a stability and compatibility release. Native replay no longer crashes on iPad when a layer holds an opaque backing object, Android replay records normally on screens that mount hidden background WebViews, and the web and React SDKs now handle older TV browsers — fewer stalls during recording, correct screenshots on apps with hidden scrollbars, and successful report preparation on runtimes missing modern browser APIs. On the dashboard side, the retired native view-tree recorder&apos;s image-asset settings are gone and the remaining video replay setting is now correctly labelled as applying to both iOS and Android.</description><pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 0.8.0</title><link>https://everframe.dev/changelog/#v0.8.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v0.8.0</guid><description>Session Vitals lands in this release across every platform: the SDKs now report video playback quality, memory and responsiveness continuously, and the dashboard gains a Sessions tab with per-session timelines and aggregate metrics. iOS, tvOS and Android reports can now carry a native video replay of the moments before the report was filed, replacing the older tree-based replay on those platforms. The dashboard splits the old Events feed into Reports and Errors with team-shared unseen state and a rebuilt error-triage page, and billing now computes and collects VAT on checkout. Session Vitals is off by default and enabled per app from the dashboard, so upgrading the SDK alone changes nothing you have not opted into.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Android Bug Report: What It Captures and What It Misses</title><link>https://everframe.dev/learn/android-bug-report/</link><guid isPermaLink="true">https://everframe.dev/learn/android-bug-report/</guid><description>An Android bug report is a device diagnostic dump, not a user&apos;s account of the problem. What it covers, what Crashlytics adds, and the gap neither one fills.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate></item><item><title>How to Run a Bug Bash That Produces Fixable Bugs</title><link>https://everframe.dev/learn/bug-bash/</link><guid isPermaLink="true">https://everframe.dev/learn/bug-bash/</guid><description>A bug bash is a timeboxed session where a whole team hunts bugs in one area at once. How to scope, run and triage one — and what makes the reports usable.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Bug Report Format: A Template That Gets Bugs Fixed</title><link>https://everframe.dev/learn/bug-report-template/</link><guid isPermaLink="true">https://everframe.dev/learn/bug-report-template/</guid><description>A bug report format you can copy, field by field, with a filled example — plus why a template is a workaround for context the report should carry itself.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Bug Reporting Tools: The Split Nobody Mentions</title><link>https://everframe.dev/learn/bug-reporting-tools/</link><guid isPermaLink="true">https://everframe.dev/learn/bug-reporting-tools/</guid><description>Most bug reporting tools are web-first browser extensions that cannot touch a native app. What each one actually captures, installs and costs to run.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Jira Bug Report: Fields, Workflow and Getting Them Filed</title><link>https://everframe.dev/learn/bug-reports-in-jira/</link><guid isPermaLink="true">https://everframe.dev/learn/bug-reports-in-jira/</guid><description>How Jira models a bug report, the Resolution field that quietly decides what counts as fixed, and the options for filing reports without typing them by hand.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Bug Triage: How to Run It Without It Becoming a Status Meeting</title><link>https://everframe.dev/learn/bug-triage/</link><guid isPermaLink="true">https://everframe.dev/learn/bug-triage/</guid><description>Bug triage decides what gets fixed and what does not. How to run it, how severity and priority differ, and why most triage meetings quietly stop working.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Session Replay Tool: Analytics Product or Debugging One?</title><link>https://everframe.dev/learn/session-replay-for-bug-reports/</link><guid isPermaLink="true">https://everframe.dev/learn/session-replay-for-bug-reports/</guid><description>Two different products share the name session replay tool. How to tell which one you are buying, what each costs, and which one fits bug reports.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate></item><item><title>What Are Bug Reports, and What Makes One Actionable?</title><link>https://everframe.dev/learn/what-is-a-bug-report/</link><guid isPermaLink="true">https://everframe.dev/learn/what-is-a-bug-report/</guid><description>What are bug reports, what belongs in one, and why the fields people skip are the ones that decide whether anybody can reproduce the problem later.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate></item><item><title>SDK for Mobile Apps: What One Is and What It Costs You</title><link>https://everframe.dev/learn/what-is-a-mobile-sdk/</link><guid isPermaLink="true">https://everframe.dev/learn/what-is-a-mobile-sdk/</guid><description>An SDK for mobile apps is code you ship inside your binary. What that buys, what it costs in size and setup, and the deprecation risk nobody prices in.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 0.4.5</title><link>https://everframe.dev/changelog/#v0.4.5</link><guid isPermaLink="true">https://everframe.dev/changelog/#v0.4.5</guid><description>iOS packaging fix: the distributed xcframeworks now carry a proper version string, so apps embedding the iOS SDK pass App Store validation. Binary-only repackage — no API changes.</description><pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 0.4.4</title><link>https://everframe.dev/changelog/#v0.4.4</link><guid isPermaLink="true">https://everframe.dev/changelog/#v0.4.4</guid><description>The 0.4.x line, June 2026. Reliability and screenshot-fidelity improvements across the JS SDKs, including a new screenshot engine that preserves nested scroll positions without touching the live page, so captures match exactly what the user was looking at.</description><pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 0.3.0</title><link>https://everframe.dev/changelog/#v0.3.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v0.3.0</guid><description>Simpler reporter API for the JS SDKs: useTraceItX().open() is now the single entry point and resolves with the submit outcome (submitted, queued, or cancelled), so you can react to what happened after a report is sent. This was a breaking change — see the migration notes in the release.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 0.2.0</title><link>https://everframe.dev/changelog/#v0.2.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v0.2.0</guid><description>The big one. Full annotation tooling landed across every platform:</description><pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate></item><item><title>Everframe 0.1.0</title><link>https://everframe.dev/changelog/#v0.1.0</link><guid isPermaLink="true">https://everframe.dev/changelog/#v0.1.0</guid><description>First public release — capture, the AI-ready envelope, and signed webhook delivery across the initial SDKs.</description><pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate></item></channel></rss>