Screensaver Certification Failing

Archived
1

I’ve tried a multitude of options to get a screensaver past static analysis, but there are two errors that I have no idea how to overcome. Even taking Roku’s github screensaver and repackaging verbatim causes these errors. Is there a different process to successfully flag/submit screensavers so they aren’t analyzed as a ‘channel’?

  1. Deep Linking is prohibited in screensavers, but you this error comes up otherwise:
    1. Channels are required to support roInput events. Please ensure your manifest includes the supports_input_launch=1 entry and your channel properly handles roInput events.
    2. Adding that entry generates the error that deep linking is not allowed in screensavers, so there’s no way I’ve found around this to enable publishing.
  2. “AppLaunchComplete” beacon is missing.
    1. I have tried multiple approaches to get around this, used various AI suggested tools and methods, etc, but I cannot find a way to fire that beacon successfully. I always receive the following error in the debug log:
      1. BRIGHTSCRIPT: WARNING: roSGNode.signalBeacon: not reachable. AppLaunchComplete not signalled: pkg:/source/…
2

I’ve tried, but I’m still having trouble getting a screensaver to post successfully. Any tips or pointers from other screensaver creators?