Unique Channel Store Name

To my knowledge, one has always been able to change the channel name - so that part is not new.

I thought the check is real-time, so there shouldn't be a delay. Can you clearly describe your situation, i am not sure i get it? E.g.
(1) had pvt channel named A 
(2) renamed A to "A test" - that worked
(3) trying to create public channel "A" fails now, showing such-and-such error

What answers in the forum say that "Roku support had to change the name"?

The #1-3 steps you outlined are the issue, exactly - step #3 fails with:

"Roku requires that names for channels within the Channel Store are unique. The name you have selected for your channel is not available. Please select a different name"

Old post suggesting Roku devs had to change it:

https://forums.roku.com/viewtopic.php?t=45323

I thought RokuJoel was referring there to swapping two names A <-> B.
I have always ass-umed that one can do it manually through "temp variable", i.e. rename A -> C, B -> A, C -> B
But maybe not. Looking forward to hear what says Roku* ...

I just tried again - same error - is there some other forum/email/etc I should be contacting to get this resolved?

I remember some similar problems. Try renaming the private channel to something that doesn't have your desired name in it at all. If you can't get it to stick make the changes and upload a pkg for that channel ( it can be the current one)

Thanks for the reply - I just tried that and no joy, same error as above.

Please Roku, what do I have to do to "fix" this?

OK, this still doesn't work today - where do I need to contact to get an actual Roku employee to fix this?

"pcnweb" wrote:
OK, this still doesn't work today - where do I need to contact to get an actual Roku employee to fix this?

In theory, developer at roku.com

Email sent, but I'm rapidly losing faith in Roku as a viable platform with these kind of simplistic issues.

"pcnweb" wrote:
Email sent, but I'm rapidly losing faith in Roku as a viable platform with these kind of simplistic issues.

Well, for some reason RokuCo still sees themselves as a boutique, as a niche platform - seems they are okay if things in the dev.portal are broken, because a human can fix it up for you behind the scenes - instead of having the self-service kiosk working.

It is well-known the Co's webbers are danger to the society - specifically over the last 2 years, when they re-invented and re-implemented something that did not need fixing. The October update demonstrated again that a 0 (zero) QA is being done for the web. I take solace in the thought that the "web team" is something completely different from the "core team"