Have you restarted the machine the Emby server is running on? It might be related to that PortMapper error and NAT Addressing. The Roku crashes because we must be expecting data and get NULLS instead. There are a few spots where NULL replies were not expected in the code and a type mismatch crashes the app. We are going through correcting this as we find them and tightening up this logic. The Roku makes the gears/cogs/mechanics required to do most things complicated. You must keep render methods in the render thread and everything else in task threads. Then communicate back and forth using fields and observers. It makes it so the Roku side can get NULL where we never anticipated. We are doing much better at this as time goes on and cleaning up the last few spots where this can happen.
We apologize this is an issue. If restart your Emby machine does not solve this can you please post server logs from a new Emby server start and after a fresh crash of the Roku app. Please SCRUB your IP/Host from these logs with find/replace. Use <SNIPPED> or <MY-IP> or similar when you replace. Don't just delete what was there we need a placeholder of what used to be there so we can read the logs properly. Thanks.
Edited by speechles, 09 November 2019 - 10:17 PM.