For what it's worth, the bug in the newer YTTV app (4.x.x) still surfaces when using voice commands ("open espn on youtube tv"). From the device logs, that voice command more or less executes the same commands that ADBTuner would.
It's something they are certainly going to fix.
It's easy to reproduce. Just keep the app open (suspended in the background) for a good while (I've seen it after six hours, could happen in less). The first deep link, no matter how it's loaded, will fail.
YTTV is just a web app.
Neat trick: if you open https://www.youtube.com/tv/upg in Chrome you can use the tv app UI in browser.
After sitting idle for a while, I believe a server side event triggers a full reload. The URL changes to /tv/upg?hrld=1. You can actually see this when using the app normally. Sometimes you open it, you see the app UI for a millisecond, then it reloads, splash screen and all.
Summary: deep link opens app, content starts loading, full reload is initiated, the deep link context is lost. The app just stops on the home screen.
I'm not going to do anything in ADBTuner to try to fix this since it's likely the bug will eventually get fixed in the app itself. I recommend turning off automatic app updates (should always be off anyway) and sideloading an older 3.x version until this is fixed.
Alternatively, you can use a "compatibility mode" style configuration which will reload the app in advance. This slows down tuning, but should work as expected.
If you use "Keep Device Awake" along with "Keep In Foreground" and YTTV configured as the "Keep Alive Package Name" that will likely avoid the issue, but it's not guaranteed.
A custom configuration that opens the app, waits X seconds, then sends the deep link might be another possible workaround. How long to wait will probably be device dependent and this will slow down tuning as well.
I pushed a new development build of ADBTuner (20260711-1) this morning. It includes two changes.
-
Restored a previously removed delay before playback detection starts. This should make the YTTV bug result in a failed tune instead of a successful tune that is just the app's home screen.
-
Fixed a bug that could cause the app that could cause a "keep in foreground" app to end up in the background if an unrelated action pushed it into the background (remote command, software update, etc.)