Status Update
Comments
al...@google.com <al...@google.com> #2
sg...@google.com <sg...@google.com> #3
al...@google.com <al...@google.com> #4
I can find the "YouTube for Google TV" app on the Google Play Store when searching through the browser on my PC. But on my phone, if I search for it on the Google Play Store it does not come up. I see the "YouTube" app suitable for my phone, which shows as "installed", and I see "Google Play Movies and TV". Same on my tablet.
On my Android TV Nexus Player, I find "YouTube for Android TV" and "Google Play Movies and TV", but not "YouTube for Google TV".
This article
would seem to explain what is going on, as well as the bitterly negative reviews for the March 2015 upgrade of the "YouTube for Google TV" app, here:
The fact that I can't install "YouTube for Google TV" on my Android TV is not surprising -- It seems clear that Google doesn't want Android TV owners to have access to it.
So, back to the original problem: It seems then that the YouTubeAPI for Android is not supported on Android TV (at least currently). So, your original question is still a good one: will Google make the YouTube API library work with the default "YouTube for Android TV" application? Maybe they really don't want the YouTube viewing experience on the living room TV to be customized in third-party apps.
ag...@google.com <ag...@google.com> #5
Thank you for this post. I am having the same problem with the default pre-installed version of YouTube on my Android TV Nexus Player. When I attempt to "UPDATE YOUTUBE APP" it doesn't actually update it. If I uninstall and re-install YouTube, it simply re-installs the same version (version 1.0.5.4, updated on Mar 26, 2015, 8.62 MB). If I uninstall that, and search on Google Play Store for the com.google.android.youtube.googletv app recommended above, it doesn't find it - it only finds the first app.
You say "But installing of second app is very inconvenient for users." - I agree - it's so inconvenient, I can't figure out even how to do it.
Would you mind telling me how you did it?
Thank you,
Lloyd
al...@google.com <al...@google.com> #6
al...@google.com <al...@google.com>
al...@google.com <al...@google.com> #7
al...@google.com <al...@google.com>
al...@google.com <al...@google.com>
ap...@google.com <ap...@google.com> #8
Nexus Player with android 5.1.1;
com.google.android.youtube.googletv is not installed (and can't be installed) and the youtube player api gives an error and suggests to update the youtube app.
Waiting for updates...
ap...@google.com <ap...@google.com> #9
al...@google.com <al...@google.com> #11
ap...@google.com <ap...@google.com> #12
ap...@google.com <ap...@google.com> #13
I'm using the API for YouTube thumbnails, and am using the onInitializationFailure callback to detect failure. When a user recoverable error happens, the YouTube app linked to from the Dialog is "not available on this device". Very confusing for users, as they can clearly see that it is there.
@Override
public void onInitializationFailure(YouTubeThumbnailView view, YouTubeInitializationResult loader) {
if (loader.isUserRecoverableError()) {
loader.getErrorDialog(activity, code).show();
}
}
ap...@google.com <ap...@google.com> #14
So, do you have the new api for android tv?
and there the address for iframe api:
al...@google.com <al...@google.com> #15
bu...@google.com <bu...@google.com> #16
It provides a YoutubeTvView that embeds a Webview with Youtube iframe with all Javascript API available from this view.
Also, YoutubeTvFragment holds a YoutubeTvView with a media control bar (PlaybackOverlayFragment)
ap...@google.com <ap...@google.com> #17
Are you folks aware of what's actually occurring out here in the world? This is the future, and can't be difficult to do. Please enable it.
bu...@google.com <bu...@google.com>
pr...@google.com <pr...@google.com> #19
na...@google.com <na...@google.com> #20
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.core:core:1.15.0-alpha02
androidx.core:core-ktx:1.15.0-alpha02
androidx.emoji2:emoji2:1.5.0-rc01
androidx.webkit:webkit:1.12.0-beta01
pr...@google.com <pr...@google.com> #21
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.activity:activity:1.10.0-alpha02
androidx.core:core-splashscreen:1.2.0-alpha02
androidx.work:work-multiprocess:2.10.0-alpha03
androidx.work:work-runtime:2.10.0-alpha03
na...@google.com <na...@google.com> #22
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.car.app:app:1.7.0-beta02
androidx.car.app:app-automotive:1.7.0-beta02
androidx.privacysandbox.ui:ui-client:1.0.0-alpha10
androidx.privacysandbox.ui:ui-provider:1.0.0-alpha10
androidx.wear.watchface:watchface-complications-data:1.3.0-alpha04
pr...@google.com <pr...@google.com> #23
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.input:input-motionprediction:1.0.0-beta05
androidx.webkit:webkit:1.12.1
na...@google.com <na...@google.com> #24
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.core:core-location-altitude:1.0.0-alpha03
na...@google.com <na...@google.com> #25
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.exifinterface:exifinterface:1.4.0-alpha01
pr...@google.com <pr...@google.com> #26
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.core:core-telecom:1.0.0-beta01
androidx.mediarouter:mediarouter:1.8.0-alpha01
androidx.transition:transition:1.6.0-alpha01
na...@google.com <na...@google.com> #27
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.browser:browser:1.9.0-alpha01
androidx.versionedparcelable:versionedparcelable:1.2.1
pr...@google.com <pr...@google.com> #28
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.tracing:tracing:1.3.0-beta01
na...@google.com <na...@google.com> #29
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.core:core-i18n:1.0.0-beta01
androidx.leanback:leanback:1.2.0-beta01
Description
R8 may double-outline platform NewApi calls when automatic outlining is enabled, so we should consider no-op'ing the
@DoNotInline
annotation when we're using an R8 version that does outlining.Looping in from email,