Hi Everyone,
I have strange problem… My Roku app I’ve created for my client Healthcasts.com intermittently quits without any errors or crush report… Problem seem to be at its worst on Roku 2 or when network is slow… But it does not happen all the time… 1 out of 5 tests…
Anyone had that issue before?
Thank you,
Peter
I would just generally suggest you adding more diagnostic feedback to various sections of your code, various stages in functions, so that you sort of get a running tally of how things are working, then when it crashes you can at least try to see what the latest things were. Rinse, repeat. Hopefully that approach can help.
Thank you, Komag… I’m going to post some out put before crash happens later… This thing is driving me batty…
The most common cause of this problem in the past has been that the app has closed all its screens.
–Mark
“pyelagin” wrote:
I have strange problem… My Roku app I’ve created for my client Healthcasts.com intermittently quits without any errors or crush report… Problem seem to be at its worst on Roku 2 or when network is slow… But it does not happen all the time… 1 out of 5 tests…
Are you talking about the published channel “Healthcasts” - or a “side-loaded” version of it (i.e. developer mode)? If the former - mind you: no diagnostics are shown in the telnet console, by design
Line of code that fixed the problem 
t = CreateObject(“roImageCanvas”)
dsp_AdPI(o) 'custom screen
t.Clear()
Thanks everyone for prompt replies…
“RokuMarkn” wrote:
The most common cause of this problem in the past has been that the app has closed all its screens.
Hm, you know what will be neat?
If some diagnostic gets logged to console in such event. Something like “Warning: screen stack empty, exiting channel.”
I have seen such complaint over and over many times, so an ounce of diagnostic here is worth a pound of troubleshooting.
Is it too hard to do?
yea I agree… Just something to let u know what’s happening… it’s a simple thing but takes a while to get ur head around it…
Yes, after reading this post yesterday I took a look to see if we can add a message for this case. I’ll file an enhancement request to do this.
–Mark
muchas gracias!
Yes, after reading this post yesterday I took a look to see if we can add a message for this case. I’ll file an enhancement request to do this.
–Mark
Mark have Roku ADD some new component(screen) for this?
I don’t understand the question. I have indeed filed an enhancement request to add a message to be printed to the debug console when the app closes because the screen stack is empty. No new components or screens are involved.
–Mark
Hi RokuMarkn,
As pyelagin says
Roku app quits with no errors,
it is possible in one condition: he is closing all the screen(in technical term i can say “Exit while” from all the screen), otherwise there would be backtrace. it means roku debug did not find any wrong here.
Sometimes when apps crash due to some reasion like: web service problem(not getting proper response from server it will happen in the case:developer have forget to check if condition for response code 200-300), or due to some other reasion in our apps UI etc.
In that case our apps crash(backtrace) and all screen close and control jump to ROKU home page.
in this situation is it possible after backtrace(crash screen) control will move to splash screen and restart our channel automattically(Not go to ROKU home page)?.
