Once your channel is built, the Roku page of your app in the Tappla dashboard lists the steps one by one, with your package, the deep link values, the store poster and the screenshots. This article explains the settings on the Roku side that most often hold a submission up.
The settings that matter
Pricing: Free.
Customer Account Requirement: leave it off. Your channel needs no sign-in: anyone who adds it can watch. If it is on, Roku expects a sign-in flow and its checks fail (see below).
In-channel products: none.
Minimum firmware version: the value shown on your Roku page (currently 15.1).
Deep link: add the three values from your Roku page under Deep Linking. Roku tests them during certification and rejects the channel without them.
Feed URL: there is none to enter. Your package already knows where your videos come from.
Ads: declare ad revenue only if your Roku package was built with ads, that is after you switched ads on in your dashboard and requested a new Roku build. Without ads, your package contains no ad code. With ads, Roku also asks for an app-ads.txt file (see below).
When Roku's checks report errors
After the upload, Roku runs a static analysis on the package. These messages all come from one setting, not from the package:
Roku says | What it means |
|---|---|
Voice keyboards are required for entering email addresses, PIN codes and passwords | Roku treats your channel as one with sign-in |
All authenticated channels must use the Request for Information (getUserData) API call | the same |
ChannelStore "getUserData" required for On-Device Authentication is missing | the same |
You have selected Customer Account Requirement … but have not enrolled in Roku Partner Payouts | this is the setting that causes all four |
What to do: switch Customer Account Requirement off in your channel's submission properties and run the checks again with the same package. You don't need to add any code, and you don't need a new package.
If an error is still there afterwards, send us a screenshot of the static analysis page and we'll look at it.
Ads and the app-ads.txt file
If your channel shows ads, Roku asks for the address of your app-ads.txt file in the Monetization setup. The file lists who is allowed to sell ads in your channel. Without ads, you don't need one.
What goes in it: the lines your ad partner gives you, usually one per seller with your publisher ID. If Roku sells part of your ad space itself, Roku shows you its lines too, and they go into the same file. We don't sell ads, so there is no line from us.
Where it goes: at the top level of the website you entered as the developer website for your channel, for example yourwebsite.com/app-ads.txt. It has to be on your own domain, which is why we can't host it for you.
If your website can't hold the file: some website builders, Wix among them, don't allow an app-ads.txt file. Then use a second domain you own as the developer website and put the file there. Simple static hosting is enough. Your ad partner may also be able to help.
The order is: ad partner first, then the file, then its address in Roku. How to switch ads on and what changes in the other stores: Ads in your TV apps.
The vanity access code
Roku gives every channel an access code. Viewers can use it to add your channel at my.roku.com without searching the Channel Store.
Roku creates one automatically, and you can keep it.
You can choose an easier one, such as YOURCHANNELNAME, in your channel's properties, as long as no other channel uses it.
It starts working once your channel is published. A beta channel has its own code for testing.
You don't need a vanity code to submit.
After Roku approves your channel
Paste the link to your channel in the Roku Channel Store into the field at the bottom of your Roku page. Your dashboard then shows the channel as live.