# Roku Is Sunsetting SGDEX and Its Testing Tools on January 31, 2027: What TV App Teams Should Do Now

> Roku ends support for SGDEX, the Unit Test Framework and Automated App Testing on Jan 31, 2027. What really breaks, what does not, and a migration plan that fits.

- URL: https://blog.w2bit.com/en/blog/roku-sgdex-sunset-what-to-do-before-january-2027
- Author: Davidson Simões
- Published: 2026-11-20
- Language: en
- Tags: smarttv, roku, brightscript, sgdex, testes, desenvolvimento
- Also available in Portuguese: https://blog.w2bit.com/blog/fim-do-sgdex-roku-o-que-fazer-ate-janeiro-2027

On November 19, 2026, Roku announced that it is sunsetting three legacy developer tools: the SceneGraph Developer Extensions (SGDEX), the Unit Test Framework and Automated App Testing. On January 31, 2027, support ends, the tools can no longer be downloaded from Roku, their GitLab repositories become read-only and their documentation leaves the developer site. Roku offers no direct replacement. For an app built on SGDEX the practical news is better than the headline: SGDEX ships inside your own package, so a published app keeps running, and the repositories are archived rather than deleted. What changes is ownership. From February 2027 the code that draws your grids, details screens and player is yours to maintain, and the two testing tools many Roku CI pipelines rely on need a replacement. Here is what the announcement says, what it does not say, and how we would plan the next ten weeks.

## TL;DR

- **Three tools, one date.** SGDEX, the Unit Test Framework and Automated App Testing lose support on January 31, 2027. Repositories are archived, downloads and docs removed.
- **Shipped apps are not switched off.** SGDEX is copied into `pkg:/components/SGDEX` of your app. Nothing in the announcement changes how published apps run.
- **No official replacement.** Roku's advice: copy the SGDEX components you use into your project, and move unit tests and automation to another approach.
- **Rooibos for unit tests, ECP for automation.** Rooibos is the community framework Roku's own engineers said they want to integrate with the RSG 2.0 SDK; Roku's WebDriver was only a translator to the External Control Protocol.
- **RSG 2.0 is not the migration target yet.** The TypeScript SDK is sideload-only during its beta, with Streaming Store publishing targeted for fall 2027.

![What SGDEX is inside a Roku app: full-screen views such as GridView, DetailsView and MediaView, the ContentManager with its ContentHandler, RAFHandler and EntitlementHandler, the ComponentController with its ViewStack, and the ButtonBar, all copied into pkg:/components/SGDEX of the app package](https://blog.w2bit.com/static/images/roku-sgdex-sunset/anatomy.en.webp)

_SGDEX already lives in your package: 117 files, 48 SceneGraph XML components and 53 BrightScript files in the current release. The sunset changes who maintains them, not where they run._

## What Roku announced on November 19

The post on the Roku Developer Blog is short and specific. On January 31, 2027, Roku stops fixing issues or answering questions about the three tools, the tools are no longer available to download or use from Roku, the GitLab repositories that hold them and their samples become read-only, and their developer documentation is removed. Until then everything stays online; the Developer Tools page already marks all three as deprecated, the same text appears in a new section of Roku's Deprecated APIs page, and the SGDEX and Automated App Testing documentation pages carry a sunset banner.

Roku's stated reason is that these are "legacy tools with low usage" and that it is "moving toward public, open-source developer tooling", so it would rather spend engineering effort on the tools and SDKs more developers use. The preparation advice is one line per tool: copy the SGDEX components you need into your own project before the repository is archived; identify the test suites that depend on the Unit Test Framework and move them to another approach; identify the automated tests and workflows that depend on Automated App Testing and replace them. Because the repositories are archived rather than deleted, you can clone them before January 31 and keep a copy.

## What SGDEX is, and why the runtime does not change

Roku describes SGDEX as "a collection of developer sample code" built from pre-built, reusable SceneGraph components, so that apps can be assembled quickly with a consistent UX. Roku calls it sample code; for the teams that adopted it, it is the UI framework their app is built on. The repository provides full-screen views (GridView, DetailsView, MediaView, SearchView, TimeGridView, CategoryListView, EntitlementView, ParagraphView and SlideShowView), a Content Manager that connects a view to a feed or API and takes care of the SceneGraph Task nodes for you, a Component Controller that manages the screen stack, a ButtonBar, and handlers for the Roku Advertising Framework and for Roku Pay subscriptions and entitlement. The last release, v2.9.1, is dated November 3, 2023; the last commit, a documentation link fix, is from February 2024. The license is Apache 2.0.

The installation instructions are the key to reading this sunset correctly. To use SGDEX you copy the `extensions/SGDEX` folder into your app at `pkg:/components/SGDEX`, copy `SGDEX.brs` into `pkg:/source`, and add `bs_libs_required=roku_ads_lib` to the manifest. There is no runtime dependency on a Roku server or on the repository: the components are compiled into your package like any other SceneGraph component. In the current archive that is 117 files, 48 XML components and 53 BrightScript files, about 1.2 MB of source. Our reading of the announcement is therefore that no published app stops working on February 1, 2027. What ends is the upstream: if a future Roku OS release changes behaviour that SGDEX relied on, nobody at Roku will ship v2.9.2.

That upstream has mattered before. The SGDEX changelog records a MediaView fix for a RAFHandler problem that appeared with Roku OS 10.5, and an earlier release that "fixed several issues where Roku's Static Analysis reported erroneous errors for SGDEX channels". Both kinds of change, OS behaviour and certification rules, keep happening. Roku's Deprecated APIs page states that Static Analysis reports deprecated APIs as errors and that all errors must be resolved to publish; its newest entry, `roHttpAgent.InitClientCertificates()`, is a warning today and becomes a publishing-blocking error on April 1, 2027. The SGDEX core does not call that function (three of its sample apps do), but the pattern is the lesson: whoever owns the copy in your repository owns the next deprecation.

## The two testing tools, and what replaces them

The Unit Test Framework is a BrightScript test runner: suites extend a `BaseTestSuite`, a runner collects and executes them on the device and prints a report, and a newer "annotation approach" borrows `@Test`, `@BeforeEach` and `@ParameterizedTest` from JUnit 5. The repository shows community fixes merged a month ago, so it is not dead code, but after January it is frozen.

The natural destination is Rooibos, the test framework maintained by the RokuCommunity group. Its README calls it "simple, mocha and junit inspired", it is MIT-licensed, and it describes itself as "an independent open-source project maintained exclusively by volunteers" with tens of thousands of tests in production. It is current: version 5.17.0 was cut in October 2026, a 6.0 alpha line is being published (alpha 58 on November 16), and an October change added Roku Cloud Emulator support to its CLI. It runs as a plugin of BrighterScript, the community superset of BrightScript that compiles to standard BrightScript. The strongest endorsement comes from Roku itself. Asked in the November 11 RSG 2.0 Q&A what the recommended unit testing tool is, Roku's engineers said they use Jest internally for the SDK, that Jest does not run on the device, and that the team "would like to integrate the BrightScript test framework Rooibos" with Jest so JavaScript and SceneGraph tests run together, which has not happened "because of bandwidth". Moving suites to Rooibos now is a step toward where Roku's own tooling is heading.

Automated App Testing is a different kind of tool. Roku shipped a Selenium-style WebDriver binary with an HTTP server and an ECP client: your Robot Framework, JavaScript or Python test sent JSON Wire Protocol commands, the WebDriver translated them into External Control Protocol requests, and the device answered with the SceneGraph XML of what was on screen. Its changelog stops at v2.3.0 in September 2021. The part that goes away is the translator; ECP itself is a documented, supported REST API over the local network, and it is what everything else uses too. Two details from the ECP documentation matter for a rebuild: since Roku OS 14.1 the device setting "Control by mobile apps" must be enabled to receive `keypress` commands, and the `query/sgnodes` family requires developer mode. ECP commands may not be issued from inside an app, and Static Analysis blocks apps that try.

There are three realistic routes. Roku Test Automation (RTA), also under RokuCommunity and MIT-licensed, drives devices with ECP plus an on-device component that reads and sets node fields, calls functions and queries focus; its README says it has more capabilities than Roku's first-party option and "does not require a Go server in the middle to convert ECP commands". The Roku Cloud Emulator, announced at the September Developer Summit and rolling out in phases, exposes virtual players and TVs through REST and WebSocket APIs built, in Roku's words, for merge checks and nightly runs: start a device from a snapshot, sideload a build, drive it with ECP key commands, capture firmware logs, stop and delete it. For real hardware in the loop, Roku's own documentation points to stb-tester, a third-party device. Roku's description of how it tests the RSG 2.0 SDK, Jest on a laptop driving a sideloaded test app through ECP and reading back the tree, is the same architecture.

![Timeline from the last SGDEX release to the RSG 2.0 publishing target: v2.9.1 on November 3, 2023; Roku Cloud Emulator and RSG 2.0 announced on September 23, 2026; sunset announced on November 19, 2026; Streaming Store blackouts from November 20 to 29 and from December 18 to January 4; support ends on January 31, 2027; InitClientCertificates blocks publishing from April 1, 2027; TypeScript store publishing targeted for fall 2027](https://blog.w2bit.com/static/images/roku-sgdex-sunset/timeline.en.webp)

_The sunset lands between two store blackouts and well before the TypeScript SDK can publish. Plan around the publishing windows, not around the sunset date._

## Dates that shape the plan

January 31 is a date for cloning and for support, not for shipping. The Roku Streaming Store is blacked out from Friday, November 20 through Sunday, November 29, 2026, and again from Friday, December 18, 2026 through Monday, January 4, 2027. Submissions during a blackout are certified but only published afterwards, and Roku says certification typically takes at least five business days. If you want a build with the vendored SGDEX and the new test setup in production before the sunset, the realistic submission windows are November 30 to December 17, and January 5 to roughly January 22. Since the runtime does not change, missing those windows costs nothing in production; what you must not miss is the clone.

Two later dates belong in the same plan. April 1, 2027 is when `InitClientCertificates()` starts blocking publishing, a reminder to run Static Analysis over your SGDEX copy in every release. And fall 2027 is Roku's target for publicly publishing TypeScript apps built with the RSG 2.0 SDK. Until then that SDK is sideload-only unless a Roku partner team enables a private beta channel, and nothing in its announced component list, FlexGrid, focus management and SolidJS integration, is a drop-in equivalent of an SGDEX GridView or MediaView. In our reading, RSG 2.0 is where new Roku UI should be designed, not a place to move an SGDEX app before the sunset.

## A migration plan that fits in ten weeks

Start with an inventory, because the three tools hide in different places. For SGDEX, search the app for components that extend SGDEX views and handlers (`GridView`, `DetailsView`, `MediaView`, `ContentHandler`, `RAFHandler`, `EntitlementHandler`), check whether `pkg:/components/SGDEX` is committed to your repository or fetched by a build script, and record which version you carry. For the Unit Test Framework, look for `UnitTestFramework.brs`, `BaseTestSuite` and the runner invocation. For Automated App Testing, look for the `RokuWebDriver` binary, the Robot or JavaScript libraries and any CI job that starts them.

Then take ownership of SGDEX deliberately. Clone the full repository, documentation included, since the `documentation` folder with the components reference, the ContentHandlers guide and the ViewStack guide disappears from Roku's site with everything else. Commit the copy you ship, pin the version and commit hash in a README, and do not plan on tracking an upstream: the GitLab project shows four imported community branches and no commits since February 2024. Add your copy to the same lint, Static Analysis and OS beta routine as the rest of your code. If you only use two or three views, this is the moment to delete the rest.

For unit tests, migrate suite by suite to Rooibos; the BrighterScript toolchain gives you a CLI that runs on a physical device or, since October, on a Roku Cloud Emulator instance. For automation, rebuild on ECP. If your tests were mostly keypress sequences plus checks for which SceneGraph node is on screen, RTA covers that with less infrastructure. If the goal is CI without a shelf of devices, ask Partner Success for Roku Cloud Emulator access and prototype one merge check: snapshot, sideload, ECP, logs. Keep a small hardware pass for playback and DRM, which emulators are not the right tool for.

## What this means for multi-platform TV teams

Our reading, not Roku's statement: this sunset fits the rest of Roku's 2026 moves. The repositories moved from GitHub to GitLab, the RSG 2.0 SDK shipped as open source under MIT, the Cloud Emulator exposes devices as APIs, and Roku has now named Rooibos as the framework it wants to integrate with. The platform is stepping back from opinionated first-party scaffolding and leaning on open, community-owned tooling plus a TypeScript future. For teams that ship the same catalogue to Tizen, webOS, Android TV, Fire TV and Roku, that is familiar: on the web-based TV platforms the UI framework and the test tooling were always yours. Roku is becoming the same kind of platform.

The decision to make now is not "SGDEX or RSG 2.0". It is whether to keep investing in a BrightScript UI you now own, with a maintenance budget and a test suite that runs in CI, or to treat the vendored SGDEX as a frozen layer and put new screens into the TypeScript SDK as its publishing path opens in 2027. Either way the test migration pays twice: Rooibos and ECP-driven automation are the tooling Roku's engineers described for the TypeScript world, so the suites you build this winter follow you across the transition.

![Migration map for the three tools Roku is sunsetting: SGDEX becomes code you vendor and own, with the repository cloned, the version pinned and Static Analysis in every release; the Unit Test Framework moves to Rooibos on the BrighterScript toolchain; Automated App Testing is rebuilt on ECP with Roku Test Automation, the Roku Cloud Emulator APIs or a hardware rig such as stb-tester](https://blog.w2bit.com/static/images/roku-sgdex-sunset/migration.en.webp)

_One destination per tool: own the UI code, move unit tests to Rooibos, rebuild automation directly on ECP._

## FAQ

### Will my Roku app stop working when SGDEX is sunset on January 31, 2027?

No. SGDEX is installed by copying its components into your app package at `pkg:/components/SGDEX`, so a published app has no runtime dependency on Roku's repository. What ends on January 31, 2027 is support, downloads and documentation; the GitLab repository becomes read-only. Future Roku OS or certification changes that affect SGDEX will have to be fixed in your own copy.

### What should I replace Roku's Unit Test Framework with?

The most common choice is Rooibos, the MIT-licensed BrightScript test framework maintained by the RokuCommunity volunteers, which had a 5.17.0 release in October 2026 and a 6.0 alpha line in November. In the November 11, 2026 RSG 2.0 Q&A, Roku's engineers said they would like to integrate Rooibos with Jest for the TypeScript SDK. Roku itself names no official replacement.

### What replaces Roku's Automated App Testing and WebDriver?

Anything that speaks the External Control Protocol (ECP), which the Roku WebDriver only translated. Options include the community project Roku Test Automation, the REST and WebSocket APIs of the Roku Cloud Emulator for CI, and hardware rigs such as stb-tester, which Roku's documentation mentions as a third-party alternative. Devices need "Control by mobile apps" enabled for keypresses and developer mode for node queries.

### Should I migrate an SGDEX app to the RSG 2.0 TypeScript SDK instead?

Not before the sunset. The RSG 2.0 SDK is in public beta, sideload-only, and Roku's target for publicly publishing TypeScript apps to the Streaming Store is fall 2027. Its components (FlexGrid, focus management, SolidJS) are not drop-in replacements for SGDEX views. Vendor SGDEX now, and plan new screens for TypeScript as the publishing path opens.

## Sources

1. Roku Developer Blog, "Legacy Roku developer tools being sunset," November 19, 2026. [https://blog.roku.com/developer/tools-sunset](https://blog.roku.com/developer/tools-sunset)
2. Roku, "Deprecated APIs" (documentation, section "Deprecated developer tools: January 31, 2027"). [https://developer.roku.com/dev/docs/deprecated-apis](https://developer.roku.com/dev/docs/deprecated-apis)
3. Roku, "SGDEX" (documentation, with sunset notice). [https://developer.roku.com/dev/docs/sgdex](https://developer.roku.com/dev/docs/sgdex)
4. Roku, "SceneGraphDeveloperExtensions" (GitLab repository and README). [https://gitlab.com/rokudev/SceneGraphDeveloperExtensions](https://gitlab.com/rokudev/SceneGraphDeveloperExtensions)
5. Roku, "SceneGraphDeveloperExtensions CHANGELOG.md" (v2.9.1, November 3, 2023). [https://gitlab.com/rokudev/SceneGraphDeveloperExtensions/-/blob/master/CHANGELOG.md](https://gitlab.com/rokudev/SceneGraphDeveloperExtensions/-/blob/master/CHANGELOG.md)
6. Roku, "unit-testing-framework" (GitLab repository and README). [https://gitlab.com/rokudev/unit-testing-framework](https://gitlab.com/rokudev/unit-testing-framework)
7. Roku, "Automated App Testing" (documentation, with sunset notice). [https://developer.roku.com/dev/docs/automated-channel-testing](https://developer.roku.com/dev/docs/automated-channel-testing)
8. Roku, "External Control Protocol (ECP)" (documentation). [https://developer.roku.com/dev/docs/external-control-api](https://developer.roku.com/dev/docs/external-control-api)
9. Roku Developer Blog, "Roku Cloud Emulator announced," September 23, 2026. [https://blog.roku.com/developer/rce](https://blog.roku.com/developer/rce)
10. Roku Developers forum, "RSG 2.0 Live Q&A - Recap," November 12, 2026. [https://forum.developer.roku.com/t/rsg-2-0-live-q-a-recap/11817](https://forum.developer.roku.com/t/rsg-2-0-live-q-a-recap/11817)
11. Roku Developer Blog, "RSG 2.0 SDK available for beta testing on October 29th," September 23, 2026. [https://blog.roku.com/developer/rsg-2-0-sdk-beta](https://blog.roku.com/developer/rsg-2-0-sdk-beta)
12. Roku Developer Blog, "2026 Roku Streaming Store publishing blackout periods announced," August 25, 2026. [https://blog.roku.com/developer/channel-store-blackouts-2026](https://blog.roku.com/developer/channel-store-blackouts-2026)
13. RokuCommunity, "rooibos" (GitHub repository and README). [https://github.com/rokucommunity/rooibos](https://github.com/rokucommunity/rooibos)
14. RokuCommunity, "roku-test-automation" (GitHub repository and README). [https://github.com/rokucommunity/roku-test-automation](https://github.com/rokucommunity/roku-test-automation)
15. RokuCommunity, "brighterscript" (GitHub repository and README). [https://github.com/rokucommunity/brighterscript](https://github.com/rokucommunity/brighterscript)
