Hi
Do you know if Roku made any changes to the validation process in the past week or so?
I try to publish a new channel, but I cannot pass the App Behavior Analysis.
I have this error
Initially, I thought it was from the app, but I tried to pass validation with an app that we published about 10 days ago; at that point, it passed. The app is now live. However, if I try to validate the same package, it now fails with the same error, which is not normal.
You need to be pushing the beacons at the appropriate time. If you fail it means you either are not sending these beacons …or… your times are way off base when you do. The beacons report in debug. They create output as they execute you can watch.
You should be able to see what is going on with them if you are off base. Then correct that and send them sooner at the correct spot if you fail. Or change how it is coded to run differently so tasks are created properly to thread your application so it runs faster. Or just give up. There are not really any other options. Don’t give up though. It isn’t as hard as it looks. You just have to be persistent and keep trying to push the app and get success. This is a learning experience.
I have multiple apps that DO fire the AppLaunchComplete beacon, as confirmed by these messages appearing on the debug console
11-02 02:24:37.017 [beacon.signal] |AppLaunchComplete ---------> Pending Render Pass
11-02 02:24:37.456 [beacon.signal] |AppLaunchComplete ---------> Duration(2993 ms : 2993 ms)
These apps all passed all ABA tests successfully over the past several months, but for the past several days, all have been consistently failing the ChannelLaunchPerformance test. This looks a lot like Roku’s ABA tests are fouled up again.
.
Instant TV Channel has correctly implemented the AppLaunchComplete beacon ever since Roku required it several years ago. There’s nothing else that I am aware of that can be done, other than to wait it out. Either Roku will fix the test, or they’ll temporarily disable the ABA requirement while they’re figuring out what to do.
This is definitely a platform error. I created a ticket with the same problem, and at least four other developers are experiencing the same issue. It’s highly unlikely that all code is starting with this problem now. I sent an email to partnersuccess@roku.com and am waiting for their response.