I posted this to Kocowa's support three days ago and no answer. Anyone here know ho to fix this?
Roku 3 model 4200X; software 12.0.0 build 4184-04
Kocowa version 2.4.0 (app on Roku)
Starting three days ago, when I click on the Kocowa channel, the “please wait wheel” goes round and round, then kicks me back to the Roku main screen. Kocowa never successfully starts.
To work around the issue, I have to remove the channel and reinstall it. Then log in to Kocowa with my eMail and password. Now Kocowa start successfully and I can watch what I want. But if I log out, the cycle starts over again and I have to remove and reinstall Kocowa to watch again.
If it helps, I did get a eMail notice the first time I had to log back in that there was an unusual log in from what turned out to be me on my account.
I do not have this issue using into Kocowa on my computer or on my wife’s Android. Just Roku.
Extra info: the problem reproduces on both TV's attached to two of the same model Roku devices
Many thanks,
-Tony
And I can’t find out if Putzette will finally admit she likes Putz! Well, not without jumping through hoops.
Hi @ToddAndMargo,
Greetings from the Roku Community!
Thanks for bringing this to our attention, and we appreciate the attempts to resolve it. We'd like to know more about this issue going on the Kocowa channel.
We just need additional information aside from the details you provided in order for our team to figure out the reason for this. Is there a reason you are logging you out of the channel after viewing content?
We'll be looking forward to your update. Thank you!
Warm regards,
Rey
> Is there a reason you are logging you out of the channel after viewing content?
Because there are several other channels that I also like to watch. Pressing home on the Roku remote or exit from Kocowa's menu makes no difference. I also turn my TV off when I am not watching it. No other channel has this problem.
I do not know if this means anything, but Kocowa can not keep track of what episode you are on. But I do not think this has anything to do with the current issue.
It is now working!