Fixed
Status Update
Comments
il...@google.com <il...@google.com> #2
Hi, thanks for reaching out to us! I'm currently looking into this issue you're seeing with startSeconds
. Will reach back with updates as soon as I have one.
il...@google.com <il...@google.com> #3
We are unable to reproduce this issue you're seeing with loadVideoById
. Can you share more details like the browser information and version in which you're able to see this?
il...@google.com <il...@google.com> #4
Hello. I can reproduce it in Firefox 124.0.2 (64-bit) for Linux. To reproduce I had to disable firefox enhanced tracking protection by clicking on shield button in address bar and toggle it off.
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #5
I'm using the latest version of Chrome (123.0.6312.106).
I can easy reproduce this issue at your demo site.
https://developers.google.com/youtube/youtube_player_demo
This issue will not appear when you use the guest mode of Chrome.
You need signed in Chrome using Google(YouTube) acount.
How to reproduce at demo page
1. You play the inline video and stop at 8 min.
2. Set Content start time 60.
3. Push [Update Player with selected options]
4. The inline Player start at 8 min.
If you use guest mode of Chrome, the inline Player start at 1 min.
I can easy reproduce this issue at your demo site.
This issue will not appear when you use the guest mode of Chrome.
You need signed in Chrome using Google(YouTube) acount.
How to reproduce at demo page
1. You play the inline video and stop at 8 min.
2. Set Content start time 60.
3. Push [Update Player with selected options]
4. The inline Player start at 8 min.
If you use guest mode of Chrome, the inline Player start at 1 min.
ap...@google.com <ap...@google.com> #6
Thanks for sharing all the information! I'm opening a report with the internal teams on your behalf. Will reach back with updates as soon as I have one.
ap...@google.com <ap...@google.com> #7
Project: platform/frameworks/support
Branch: androidx-main
commit fa788954621181fa8131961688634d7f739a354b
Author: Jeremy Woods <jbwoods@google.com>
Date: Thu Jul 29 16:12:29 2021
Bump androidx.test.core to 1.4.0
Test Core 1.4.0 has some fixes that allows it to work with Android S. We
should update our dependency so that all libraries that depend on test
core will be compatible with Android S.
This was previously reverted in aosp/1773211 due to failures in a number
of large test (i.e.
https://android-build.googleplex.com/builds/tests/view?invocationId=I63900009972892409 ).
Those failures have been addressed by adding explicit dependencies on
the affected libraries. The failures in camera, compose-material,
compose-ui-inspection, and media2 seem to be unrelated to this change.
RelNote: "Libraries that depend on the `Test Core` library have been
upgraded to version `1.4.0` and will now work with Android platform
version S."
Test: ./gradlew bOS
Bug: 189353863
Change-Id: I88b726b2d76735ac012ea47298e0bf02092cd857
M benchmark/benchmark-junit4/build.gradle
M compose/ui/ui-inspection/build.gradle
M gradle/libs.versions.toml
M lifecycle/integration-tests/kotlintestapp/build.gradle
M window/window-testing/build.gradle
M window/window/build.gradle
https://android-review.googlesource.com/1780300
Branch: androidx-main
commit fa788954621181fa8131961688634d7f739a354b
Author: Jeremy Woods <jbwoods@google.com>
Date: Thu Jul 29 16:12:29 2021
Bump androidx.test.core to 1.4.0
Test Core 1.4.0 has some fixes that allows it to work with Android S. We
should update our dependency so that all libraries that depend on test
core will be compatible with Android S.
This was previously reverted in aosp/1773211 due to failures in a number
of large test (i.e.
Those failures have been addressed by adding explicit dependencies on
the affected libraries. The failures in camera, compose-material,
compose-ui-inspection, and media2 seem to be unrelated to this change.
RelNote: "Libraries that depend on the `Test Core` library have been
upgraded to version `1.4.0` and will now work with Android platform
version S."
Test: ./gradlew bOS
Bug: 189353863
Change-Id: I88b726b2d76735ac012ea47298e0bf02092cd857
M benchmark/benchmark-junit4/build.gradle
M compose/ui/ui-inspection/build.gradle
M gradle/libs.versions.toml
M lifecycle/integration-tests/kotlintestapp/build.gradle
M window/window-testing/build.gradle
M window/window/build.gradle
jb...@google.com <jb...@google.com> #8
This has been fixed internally and will be available in the Fragment 1.4.0-alpha07
release.
Description
Version used: 1.4.0-alpha01
Devices/Android versions reproduced on: Android S
It's currently not possible to build an app which depends on fragment-testing for Android S since it depends on androidx.test:core:1.3.0 which does not properly export activities with intent filters.
androidx.test:core:1.4.0 fixes this.