Closed TwitchBronBron closed 2 years ago
Interesting. I've not personally seen it crash there, and the init()
for SceneManager sets m.groups = []
, so not sure why it would be undefined at that point.
Easy enough to add a check for - but a little odd. May need to investigate further.
I haven't run into this yet. Is this still happening for you guys after merging #544?
Just ran into a startup crash myself using latest dev but it's a different line. Not sure if related.
Edit: This is the third unique startup crash that traces back to scenemanager. They seem related somehow. Edit2: Just had it happen again. I've ran the debugger maybe 20 times today? so that's a ~10% failure rate for me
Just happened to me as well. Same spot as @cewert
Still happening on latest version of master. Crashed on me the second time I ran the debugger 😢
Actually this is a bigger problem than I thought. m.content
is invalid at this point, which is bizarre given it's set in the init()
. I guess we could try calling findNode()
again at this point if it's invalid in case there's something causing it not to be set on the initial call.
If it's invalid we could not try to push the scene - would just need to test how this appears to the user, and whether we'd want to acknowledge something went wrong.
I spoke with a Roku developer friend about this issue a month ago, and if I remember correctly, I think there's actually some quirks around extending ContentNode
. Could SceneManager
extend Group
instead, and just add the content
field directly to SceneManager
's interface?
The only thing that should be using content
is the SceneManager
itself, so shouldn't even need added to the interface. I've just changed it to extent Group
and with no other changes it all seems to be working properly.
Will need to do a fair bit more testing to confirm it's not broken anything else, and even more to see if it stops the error occurring - but that change and some extra checking or try/catch's certainly shouldn't hurt.
@TwitchBronBron Thanks for your help. Are these weird roku quirks documented anywhere online? or should we start our own list?
Recently stumbled on this page where you talk about using callfunc() without parameters for example. Hoping you have more of these typed up somewhere I haven't found yet 🙏
@TwitchBronBron Thanks for your help. Are these weird roku quirks documented anywhere online? or should we start our own list?
Recently stumbled on this page where you talk about using callfunc() without parameters for example. Hoping you have more of these typed up somewhere I haven't found yet 🙏
I'm not aware of this being documented anywhere, and I don't really know of somewhere that documents other weird quirks. RokuCommunity did start a website for documenting common patterns and stuff, so perhaps that would be the eventual place where something like this would go, but there's not a lot of content on there yet.
Describe the bug
Sideloading the app causes a crash, but only occasionally. It's hard to reproduce. I'm a little behind, running 5bf3a6863411cfcacde37d88c98ac725d45eaa37 so perhaps someone has already solved this issue?
To Reproduce
Expected behavior
Don't crash.
Logs These might be from several runs, and it has some of the vscode extension logging included as well. I don't see anything stick out as helpful.