The reason it works that way is you are supposed to preview the build on a device before actually submitting it. Since this is a private beta and I always have just pulled it off my device, that is never necessary but I understand why they have it done this way.
I dont mean, test the app. Obviously you do when you upload zips to the roku, then run the packager and obtain the pkg.
I meant, as a private channel with no approval process, it is quite odd. You upload the pkg file to roku, and check the im not a robot box, then hit upload. After that it shows your pkg staged, you then have to do the extra step to submit.
I guess this is to avoid the perhaps common "oh shi7, I uploaded wrong one!" type mistakes. After you upload, then you verify the right one was uploaded and hit submit. Its that eztra step of having to hit submit after you upload that is easy to miss. The submit button appears offscreen at the bottom you have to scroll to. You have to remember everytime to scroll down there and press it.
As a public channel, I see the reasoning for submit after upload. But the potential to forget to click that is always high.
This is what I meant by it isnt your fault the app didnt update, even though it was you that forgot to hit submit. It is rokus ridiculous flow of click this, click that, to get the app updated.
Sent from my Nexus 7 using Tapatalk