We are testing a non-video Roku app that primarily displays live data with periodic updates. The app fetches and updates data dynamically without any user interaction for extended periods. However, despite this continuous data flow, the app unexpectedly exits after 4 to 5 hours, showing the following log message:
status=exit exit code=EXIT_USER_NAV
Does anyone have any idea how to resolve this or understand what might be causing it? Any suggestions or workarounds would be greatly appreciated!
This is intentional. If there is no user interaction, Roku OS will periodically return to the home screen as Roku OS devices are intended for consumer streaming use. There is not a way for an application to prevent this closure.
This sounds like something best answered on the Roku developer forums:
https://community.roku.com/t5/Developers/ct-p/channel-developers
Should add that Roku's have a bandwidth saver that is normally on by default. If there is no remote usage over 4 hours, it will shut the app down. (Settings/Network/bandwidth saver). I doubt if an app can override that.
This is intentional. If there is no user interaction, Roku OS will periodically return to the home screen as Roku OS devices are intended for consumer streaming use. There is not a way for an application to prevent this closure.
Thank you for the clarification. I understand that Roku OS is designed to return to the home screen after periods of inactivity. However, our app is a live data application (not a video streaming app), and it continuously updates the UI with new data.
Is there any official or recommended approach to ensure the app remains active for extended periods without requiring constant user interaction? For example, would periodic UI updates, background tasks, or specific API calls help prevent the automatic exit?
Any insights or best practices on handling this scenario would be greatly appreciated.
Thanks
If the user isn't interacting, you could try to implement it as a screensaver app.
Allaico51@gmail.com