Private Channels not Updating

Two weeks ago the Co pushed a new version of the portal, which broke some things - sounds yours is one of them. 
Email developer at roku.com about this, let us know here what the resolution was. If you don't hear from them within two days, keep re-sending 🙂

I am also having trouble getting a submitted build (which are essentially private channels) to show up on my Ultra.  

"adamkaz1" wrote:
I am also having trouble getting a submitted build (which are essentially private channels) to show up on my Ultra.  

Tell us more? I know you know what you are talking about, so issue must be for real. 
The Co has not admitted such issue yet, though i saw vague beating around the bushes at https://github.com/rokudev/docs/issues/6

PS. on a side note - were you never unable to recover the old name "adamkaz" since the forum "snow blindness" change? My suspicion on difficulty staying logged in was about AWS load (un)balancer in front of multiple servers. 

Still no response from developer@roku.com
Private channels still not updating though the new package version says "Published" in my account...
Getting frustrated with Roku.

hey - looks like my old name is working again.  I received confirmation from Roku that there was a problem with "activation and adding channels".  After posting yesterday, I noticed there was a service bulletin on the Roku home page. It also caused the web service API to go down - I have about 5 hours of failed attempts validating purchases yesterday.  It seems to be fixed now.

I just tried updated my private channel again. No success. In my developer portal is says the new build is published but it does not update on my Roku player. 

The nice people at Roku resolved my problem...
When I was publishing an update to my private channel, i was setting the minimum firmware version to a lower version than my published channel. Apparently any already published channels with a higher version number will cause the updated channel with the lower version not to update on my Roku player. This was something I didn't take into account or now about.
Thanks and I'm glad I can continue onto my Roku developing skills!

"sparkerman" wrote:
When I was publishing an update to my private channel, i was setting the minimum firmware version to a lower version than my published channel. Apparently any already published channels with a higher version number will cause the updated channel with the lower version not to update on my Roku player. This was something I didn't take into account or now about.

Wait, what? I thought min.firmware requirement was defined to only "increase monotonically", i.e. not letting you go back.
Seems more like a bug in the implementation rather than faulty design. I.e. the DB query is wrong, it should be something like (simplifying, in reality it should be at least a join to handle all channels on account):

SELECT TOP 1 bundle# FROM bundle_bag 
WHERE channel# = :ID 
AND min_firmware# <= :PLAYER_FW# 
AND version# > :INSTALLED_VER 
ORDER BY version# DESC

... and what they are doing is sorting by min_firmware or unsorted. It's tricky but not hard if you think about the case.

I probably didn't explain it all correctly.
My original channels were posted with a firmware version v5xx. I was trying to update the channel with a firmware version of v2.xxx, which would not update on my player which is running v7.xxx
If I had a player that was running v2.xxx, then the channel would have updated. My private channels are for many corporate offices that use them for training and at trade shows. I never know what firmware version they are running so I thought it would be best to update with the lowest possible. In my case, that was not smart thinking.
Knowing what minimum firmware version to use isn't something I clearly undestand.

"sparkerman" wrote:
I probably didn't explain it all correctly.

I think I understood it correctly the first time.
For a given channel# and playerID, it should be selecting the highest version# of your app from all that are compatible with the firmware.
The newly uploaded bundle had it's version bumped up, did it not? You should always, always increase the version (both in zip and in web portal - and of course keep the two in sync).

And if you did that, Roku is in the wrong here (buggy). If OTOH you are uploading the same version again and again... all bets are off, this is PEBKAC